| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2023-05-11 release announcement draft |
| Date: | 2023-05-08 02:34:02 |
| Message-ID: | CAApHDvrmmWCxnjMR46sTvrUTP9f66j74+FMJ8eJxgEMdaTwGwg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks for working on this.
On Sun, 7 May 2023 at 15:37, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> Please provide any suggestions, corrections, or notable omissions no
> later than 2023-05-11 0:00 AoE.
For this one:
> * Fix partition pruning logic for partitioning on boolean columns when using a
> `IS NOT TRUE` condition.
Just to explain this a little further: Effectively the code thought
"IS NOT TRUE" meant "IS FALSE", and "IS NOT FALSE" meant "IS TRUE".
That was wrong because each of the NOT cases should have allowed
NULLs.
Maybe the wording can be adjusted to mention NULLs. Maybe something
along the lines of:
* Fix partition pruning bug with the boolean "IS NOT TRUE" and "IS NOT
FALSE" conditions. NULL partitions were accidentally pruned when they
shouldn't have been.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 盏一 | 2023-05-08 02:38:29 | Re: Proposal for Prototype Implementation to Enhance C/C++ Interoperability in PostgreSQL |
| Previous Message | Richard Guo | 2023-05-08 02:30:05 | Re: Introduce join_info_array for direct lookups of SpecialJoinInfo by ojrelid |