Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ts8YU-00FmaL-JF for pgsql-bugs@arkaria.postgresql.org; Tue, 11 Mar 2025 22:58:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ts8YS-008rlX-FU for pgsql-bugs@arkaria.postgresql.org; Tue, 11 Mar 2025 22:58:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ts8YS-008rlO-6n for pgsql-bugs@lists.postgresql.org; Tue, 11 Mar 2025 22:58:32 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ts8YO-002K47-1m for pgsql-bugs@lists.postgresql.org; Tue, 11 Mar 2025 22:58:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=j0fohTDkL4ZZQBUvH7GCPHlMXEboopfeu4VbVbdfQCY=; b=MJ4wq gB8ldH+hExJGadTp3N88C1RagtSHRjJyuwaAgYuPO+pHbYrkCU4S+t8jUzEenEZkGcaW7dkBFu74Z 2/jtM1OPLfy13KEdSQTBXfb8fqXjRMm9L++hOBMDfgDyG1wYoo6fM7NgEkF886PH2FslOGQ2y6KWa CrT8YIOwxvVWT9I36dbav1NMn0qTnU8n87rehqJQpnC9LyaBZFSuygDvLNLj70atklz/dE9xW7Qkf hT+xiEiv7ydh6ItuL+hGMkwSv/N1GP6e/FKCI61zUInohMoiGY1yroOyn8p/6WsP5xSHPkWIaRXwY 7xXq/W54pHJ+tIA45zb0xvL5LIeOA==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1ts8YN-007qIC-05; Tue, 11 Mar 2025 18:58:27 -0400 Date: Tue, 11 Mar 2025 18:58:27 -0400 From: Bruce Momjian To: Tom Lane Cc: Richard Guo , David Rowley , Ronald Cruz , pgsql-bugs@lists.postgresql.org, Peter Ford , "Aaron J. Garcia" Subject: Re: Query result differences between PostgreSQL 17 vs 16 Message-ID: References: <2337383.1740630494@sss.pgh.pa.us> <2748914.1740757698@sss.pgh.pa.us> <3650809.1741015351@sss.pgh.pa.us> <1837979.1741731589@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1837979.1741731589@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Mar 11, 2025 at 06:19:49PM -0400, Tom Lane wrote: > Bruce Momjian 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.