Re: why partition pruning doesn't work? - Mailing list pgsql-hackers

From Amit Langote
Subject Re: why partition pruning doesn't work?
Date
Msg-id e6e751ea-0db4-0e7b-9513-97460edb60b3@lab.ntt.co.jp
Whole thread Raw
In response to Re: why partition pruning doesn't work?  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: why partition pruning doesn't work?
List pgsql-hackers
On 2018/06/06 14:10, David Rowley wrote:
> I then decided that
> I didn't like the way we need to check which params are in the Expr
> each time we call partkey_datum_from_expr. It seems better to prepare
> this in advance when building the pruning steps. I started work on
> that, but soon realised that I'd need to pass a List of Bitmapsets to
> the executor. This is a problem as Bitmapset is not a Node type and
> cannot be copied with COPY_NODE_FIELD(). Probably this could be
> refactored to instead of passing 3 Lists in the PartitionPruneStepOp
> we could invent a new node type that just has 3 fields and store a
> single List.

I wonder why we need to create those Bitmapsets in the planner?  Why not
in ExecSetupPartitionPruneState()?  For example, like how
context->exprstates is initialized.

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Test patch for partitionwise join with partitioned tablescontaining default partition
Next
From: Rajkumar Raghuwanshi
Date:
Subject: Re: Test patch for partitionwise join with partitioned tablescontaining default partition