Postgres Pro
Downloads
Home   >   mailing lists

Re: IN operator causes sequential scan (vs. multiple OR expressions) - Mailing list pgsql-performance

From Tom Lane
Subject Re: IN operator causes sequential scan (vs. multiple OR expressions)
Date
Msg-id 24016.1169941986@sss.pgh.pa.us
Whole thread Raw
In response to IN operator causes sequential scan (vs. multiple OR expressions)  (Ryan Holmes <ryan@hyperstep.com>)
Responses Re: IN operator causes sequential scan (vs. multiple OR expressions)  (Ryan Holmes <ryan@hyperstep.com>)
List pgsql-performance
Tree view 
Ryan Holmes <ryan@hyperstep.com> writes:
> I have a relatively simple query where the planner chooses a
> sequential scan when using the IN operator but chooses an index scan
> when using logically equivalent multiple OR expressions.

EXPLAIN ANALYZE for both, please?

If you set enable_seqscan = off, does that force an indexscan, and if so
what does EXPLAIN ANALYZE show in that case?

            regards, tom lane

pgsql-performance by date:

Previous
From: Ryan Holmes
Date:
Subject: IN operator causes sequential scan (vs. multiple OR expressions)
Next
From: Ryan Holmes
Date:
Subject: Re: IN operator causes sequential scan (vs. multiple OR expressions)