Re: Query planner wants to use seq scan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bertrand Paquet <bertrand(dot)paquet(at)doctolib(dot)fr>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Query planner wants to use seq scan
Date: 2015-10-27 12:03:12
Message-ID: 21872.1445947392@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Bertrand Paquet <bertrand(dot)paquet(at)doctolib(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bertrand Paquet 2015-10-27 13:06:28 Re: Query planner wants to use seq scan
Previous Message Alex Ignatov 2015-10-27 11:30:45 Re: Query planner wants to use seq scan