public inbox for [email protected]  

help / color / mirror / Atom feed

From: Richard Guo <[email protected]>
To: Tender Wang <[email protected]>
Cc: SATYANARAYANA NARLAPURAM <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Bug: var_is_nonnullable() gives wrong results for old/new in RETURNING
Date: Fri, 10 Apr 2026 15:58:31 +0900
Message-ID: <CAMbWs4_Kd4Ep6ufUWLG78ZTAbFcZ-rriY8YQ1zd3iqFqtRnGPQ@mail.gmail.com> (raw)
In-Reply-To: <CAMbWs48swa+F+HmsxnVqYrSvDFgp9v7ShSjac5FsG4oFFKvs2w@mail.gmail.com>
References: <CAHg+QDfaAipL6YzOq2H=gAhKBbcUTYmfbAv+W1zueOfRKH43FQ@mail.gmail.com>
	<CAHewXN=9mf6NCeHE=7jUVhM_Ur=oW8R7hgfQwcvyWCSLC8VERw@mail.gmail.com>
	<CAMbWs48swa+F+HmsxnVqYrSvDFgp9v7ShSjac5FsG4oFFKvs2w@mail.gmail.com>

On Fri, Apr 10, 2026 at 2:48 PM Richard Guo <[email protected]> wrote:
> The patch also LGTM.  I also checked if has_notnull_forced_var() has
> the same issue, but it doesn't: Vars with non-default returning type
> only appear in the RETURNING clause, so they never show up in WHERE/ON
> clauses.

I pushed the patch after a bit cosmetic tweaks.  I also decided to put
the test cases in returning.sql, which I think is a better place.

Thanks for the report and the patch.

- Richard

view thread (4+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Bug: var_is_nonnullable() gives wrong results for old/new in RETURNING
  In-Reply-To: <CAMbWs4_Kd4Ep6ufUWLG78ZTAbFcZ-rriY8YQ1zd3iqFqtRnGPQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox