Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
Дата
Msg-id CAH2-Wzm7Hq69evXDC2Q3BU+HWm-s9w7qdBpXuNK8PraRweSkpA@mail.gmail.com
обсуждение исходный текст
Ответ на Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT  (benoit <benoit@hopsandfork.com>)
Ответы RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT  (benoit <benoit@hopsandfork.com>)
Список pgsql-performance
On Mon, Jun 12, 2023 at 1:17 PM benoit <benoit@hopsandfork.com> wrote:
> Is there a misusage of my indexes?
>
> Is there a limitation when using ANY or IN operators and ordered LIMIT behind?

It's complicated. Do you find that you get satisfactory performance if
you force a bitmap index scan? In other words, what is the effect of
"set enable_indexscan = off" on your original query? Does that speed
up execution at all? (I think that this approach ought to produce a
plan that uses a bitmap index scan in place of the index scan, without
changing anything else.)

--
Peter Geoghegan



В списке pgsql-performance по дате отправления:

Предыдущее
От: benoit
Дата:
Сообщение: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
Следующее
От: benoit
Дата:
Сообщение: RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT