Re: Query result differences between PostgreSQL 17 vs 16
Bruce Momjian <bruce@momjian.us>
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-12T01:56:03Z
Lists: pgsql-bugs
On Tue, Mar 11, 2025 at 08:57:06PM -0400, Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > 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? > > If you want somebody to review that patch, shouldn't it be in the CF? Uh, I wasn't sure if it would make it in the next minor release if I did that. Is it a good idea? -- 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
-
Avoid NullTest deduction for clone clauses
- bc5a08af3c44 17.5 landed
- 716a051aaccd 18.0 landed
-
Add better handling of redundant IS [NOT] NULL quals
- b262ad440ede 17.0 cited