On Wed, May 6, 2020 at 12:20 PM Steve Pritchard
wrote:
> Version: Postgres 9.6.3 production system (but also tested on Postgres 12)
>
> For my query the Planner is sometimes choosing an execution plan that uses
> "Bitmap And" (depending on the parameters):
>
> -> Bitmap Heap Scan on observation
On Wed, May 06, 2020 at 05:19:48PM +0100, Steve Pritchard wrote:
> Version: Postgres 9.6.3 production system (but also tested on Postgres 12)
>
> For my query the Planner is sometimes choosing an execution plan that uses
> "Bitmap And" (depending on the parameters):
>
> The Planner then carries t
Version: Postgres 9.6.3 production system (but also tested on Postgres 12)
For my query the Planner is sometimes choosing an execution plan that uses
"Bitmap And" (depending on the parameters):
-> Bitmap Heap Scan on observation (cost=484.92..488.93 rows=1 width=203)
(actual time=233.129..330.8