Re: [HACKERS] path toward faster partition pruning - Mailing list pgsql-hackers

From Amit Langote
Subject Re: [HACKERS] path toward faster partition pruning
Date
Msg-id c5331ff6-8b31-0742-758e-bd7b9aeddf07@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] path toward faster partition pruning  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] path toward faster partition pruning  (David Rowley <david.rowley@2ndquadrant.com>)
Re: [HACKERS] path toward faster partition pruning  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
On 2018/04/04 14:42, Amit Langote wrote:
> Attached v48.

I had forgotten to remove the static_pruning parameter I had added in the
v47, because it is no longer used.  Static pruning now occurs even if a
step contains all Params, in which case each of
get_matching_hash/list/range_bounds() functions returns offsets of all
non-null datums, because the Params cannot be resolved to actual values
during static pruning.

Also, a few changes to get_matching_partitions that David had proposed in
his delta patch but I had failed to include them in v48.

Attached v49.

Thanks,
Amit

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [HACKERS] Runtime Partition Pruning
Next
From: David Rowley
Date:
Subject: Re: [HACKERS] path toward faster partition pruning