From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: Japin Li <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: <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>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Sun, 01 Oct 2023 09:54:22 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1617076.1696121892.1@sss.pgh.pa.us>
Date: Sat, 30 Sep 2023 20:58:12 -0400
Message-ID: <1617077.1696121892@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1617077.1696121892%40sss.pgh.pa.us>
Precedence: bulk

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