Postgres Pro
Downloads
Home   >   mailing lists

Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT - Mailing list pgsql-performance

From Peter Geoghegan
Subject Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
Date
Msg-id CAH2-Wzm7Hq69evXDC2Q3BU+HWm-s9w7qdBpXuNK8PraRweSkpA@mail.gmail.com
Whole thread Raw
In response to Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT  (benoit <benoit@hopsandfork.com>)
Responses RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT  (benoit <benoit@hopsandfork.com>)
List pgsql-performance
Tree view 
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 by date:

Previous
From: benoit
Date:
Subject: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
Next
From: benoit
Date:
Subject: RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT