Horton

Re: Query result differences between PostgreSQL 17 vs 16

Richard Guo <guofenglinux@gmail.com>

View thread View on postgr.es
From: Richard Guo <guofenglinux@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, David Rowley <dgrowleyml@gmail.com>, Ronald Cruz <cruz@rentec.com>, pgsql-bugs@lists.postgresql.org, Peter Ford <pford@rentec.com>, "Aaron J. Garcia" <agarcia@rentec.com>
Date: 2025-03-04T07:30:26Z
Lists: pgsql-bugs 
On Tue, Mar 4, 2025 at 12:22 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Richard Guo <guofenglinux@gmail.com> writes:
> > Here is an updated patch, which also includes the test case you found
> > proving the no-clone-quals limitation in restriction_is_always_false
> > is also needed.

> LGTM.

Pushed and back-patched to v17.  The fix will be included in next
minor release (17.5).

Thanks
Richard

Commits

  1. Avoid NullTest deduction for clone clauses

  2. Add better handling of redundant IS [NOT] NULL quals