Horton

Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
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
Date: 2023-10-01T00:58:12Z
Lists: pgsql-bugs 
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

Commits

  1. psql: Set variables from query result on failure when printing tuples