Re: IN operator causes sequential scan (vs. multiple OR expressions)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: IN operator causes sequential scan (vs. multiple OR expressions)
Дата
Msg-id 24016.1169941986@sss.pgh.pa.us
обсуждение исходный текст
Ответ на IN operator causes sequential scan (vs. multiple OR expressions)  (Ryan Holmes <ryan@hyperstep.com>)
Ответы Re: IN operator causes sequential scan (vs. multiple OR expressions)  (Ryan Holmes <ryan@hyperstep.com>)
Список pgsql-performance
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 по дате отправления:

Предыдущее
От: Ryan Holmes
Дата:
Сообщение: IN operator causes sequential scan (vs. multiple OR expressions)
Следующее
От: Ryan Holmes
Дата:
Сообщение: Re: IN operator causes sequential scan (vs. multiple OR expressions)