Ryan Holmes <ryan(at)hyperstep(dot)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
In response to
pgsql-performance by date
|Next:||From: Ryan Holmes||Date: 2007-01-28 01:34:12|
|Subject: Re: IN operator causes sequential scan (vs. multiple OR expressions) |
|Previous:||From: Ryan Holmes||Date: 2007-01-27 23:34:56|
|Subject: IN operator causes sequential scan (vs. multiple OR expressions) |