Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)

Поиск
Список
Период
Сортировка
От Michael Lewis
Тема Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)
Дата
Msg-id CAHOFxGo0mB+9WFBgFyZh3UzUkrpJ58cbx5t8W7D-qz6_YLc_Mw@mail.gmail.com
обсуждение исходный текст
Ответ на Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)  (Dmitry Koterov <dmitry.koterov@gmail.com>)
Ответы Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)  (Dmitry Koterov <dmitry.koterov@gmail.com>)
Список pgsql-general
Дерево обсуждения
Your query and explain analyze output do not seem to match.

Filter: (cred_id = '1001344096118566254'::bigint)

I don't see anything like that in your query, nor an index that would support accomplishing that without filtering after fetching the 184k rows initially like the planner does.

В списке pgsql-general по дате отправления:

Предыдущее
От: Moris Rumenov Vrachovski
Дата:
Сообщение: Vulnerability PostgreSQL 11.2
Следующее
От: Dmitry Koterov
Дата:
Сообщение: Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)