Re: RANGE partition pruning can still exclude the default partition - Mailing list pgsql-hackers

From David Rowley
Subject Re: RANGE partition pruning can still exclude the default partition
Date
Msg-id CAApHDvr=vpLEED1fxtBgbdyud40kxHczSKOFUG23hnizE9jBfQ@mail.gmail.com
Whole thread
In response to Re: RANGE partition pruning can still exclude the default partition  (Ewan Young <kdbase.hack@gmail.com>)
List pgsql-hackers
On Fri, 18 Sept 2026 at 15:01, Ewan Young <kdbase.hack@gmail.com> wrote:
> v3 looks good to me. The nvalues == 1 restriction on the first-key
> MINVALUE/MAXVALUE trim is a clear improvement: the leading single-key
> step already trims the default there, and the BTEqualStrategyNumber
> block handles the multi-key prefixes, so the intersection removes the
> default without repeating the first-key check in every step.  Your
> comment rewrite explains the interaction much better than my original;
> agreed it was too thin.
>
> Happy with the adjustments -- thanks for picking this up.

OK thanks. I did a bit more work on the tests and pushed.

David



pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Allow pg_read_all_stats to read replication origin status
Next
From: Pavel Stehule
Date:
Subject: different result of regexp_instr than on Oracle