Re: BUG #19412: Wrong query result with not null constraint

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: s(dot)shinderuk(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #19412: Wrong query result with not null constraint
Date: 2026-02-19 02:18:54
Message-ID: CAMbWs48EjWX7W277X31ogdu4MzqOHbFATZOPqT3obgUS4Aa3sA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Feb 18, 2026 at 6:50 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> Here is a more readable version of the patch.

Regarding back-patching, I plan to back-patch this all through to v16.
Although the reported case does not seem to cause problems in v16, the
underlying logic error persists. Leaving incorrect varnullingrels in
the tree seems like a trap for the unwary.

Any thoughts?

- Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-02-19 05:26:16 BUG #19413: ASAN: stack-buffer-overflow in foldcase_options() with invalid ICU language tag
Previous Message Richard Guo 2026-02-19 01:49:44 Re: BUG #19412: Wrong query result with not null constraint