Horton

Re: Query result differences between PostgreSQL 17 vs 16

Bruce Momjian <bruce@momjian.us>

View thread View on postgr.es
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Richard Guo <guofenglinux@gmail.com>, 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-11T22:58:27Z
Lists: pgsql-bugs 
On Tue, Mar 11, 2025 at 06:19:49PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Uh, if we fixed this for NULL optimization and backpatched, should we do
> > the same for:
> > 	Parameter NOT NULL to CREATE DOMAIN not the same as CHECK (VALUE IS NOT NULL)
> > 	https://www.postgresql.org/message-id/flat/173591158454.714.7664064332419606037%40wrigleys.postgresql.org
> 
> This is unrelated to that.

Well, I was trying to figure out if we should be changing the NULL
handling in 17.X, but now that you have done it with one patch, it seems
the above URL patch should also be applied and backpatched to 17, no?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.

Commits

  1. Avoid NullTest deduction for clone clauses

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