Ryan Holmes <ryan@xxxxxxxxxxxxx> 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
