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

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

On Wed, Feb 18, 2026 at 9:03 PM Sergey Shinderuk
<s(dot)shinderuk(at)postgrespro(dot)ru> wrote:
> I'm not familiar with the code, just curios. There is a long comment
> above saying "You might think we need to adjust var->varnullingrels, but
> that shouldn't need any changes." Doesn't it need an update?

No, I don't think we need to update it. That comment explains why
varnullingrels do not require translation (since they are outer join
relids, not baserel relids). It's unrelated to what this patch does,
which is about propagating varnullingrels into the translated Var.

- Richard

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2026-02-19 02:18:54 Re: BUG #19412: Wrong query result with not null constraint
Previous Message surya poondla 2026-02-18 22:32:01 Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY