Re: Query planner wants to use seq scan
От | Tom Lane |
---|---|
Тема | Re: Query planner wants to use seq scan |
Дата | |
Msg-id | 21872.1445947392@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Query planner wants to use seq scan (Bertrand Paquet <bertrand.paquet@doctolib.fr>) |
Ответы |
Re: Query planner wants to use seq scan
Re: Query planner wants to use seq scan |
Список | pgsql-performance |
Bertrand Paquet <bertrand.paquet@doctolib.fr> writes: > We have a slow query. After analyzing, the planner decision seems to be > discutable : the query is faster when disabling seqscan. See below the two > query plan, and an extract from pg_stats. > Any idea about what to change to help the planner ? Neither one of those plans is very good: you're just hoping that the Filter condition will let a tuple through sooner rather than later. If you care about the performance of this type of query, I'd consider creating an index on (organization_id, status, handled_by) so that all the conditions can be checked in the index. regards, tom lane
В списке pgsql-performance по дате отправления: