From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Japin Li <japinli@hotmail.com>
Cc: amutu@amutu.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Date: Sat, 30 Sep 2023 20:58:12 -0400
Message-ID: <1617077.1696121892@sss.pgh.pa.us> (raw)
In-Reply-To: <ZRjDPucJiWKDJnkf@paquier.xyz>
References: <18134-87126d90cb4dd049@postgresql.org>
<MEYP282MB1669351F137C61C19FA9749BB6C2A@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM>
<ZRizujD8HMMpSXG5@paquier.xyz>
<1615012.1696121047@sss.pgh.pa.us>
<ZRjDPucJiWKDJnkf@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> FWIW, I am not excited about a backpatch, so I would keep this as a
> HEAD-only change. Sure, the existing behavior is incorrect, but it
> would be more annoying to break somebody's script flow after a minor
> release. And that's not critical.
> (If you want to fix that yourself, please feel free. I can do that
> tomorrow by myself but life keeps me busy today and I don't have any
> room to keep an eye on the buildfarm.)
I'm content to wait a day and see if anybody wants to make an
argument for back-patching.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, japinli@hotmail.com, amutu@amutu.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
In-Reply-To: <1617077.1696121892@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox