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

From Tom Lane
Subject Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Date
Msg-id 1617077.1696121892@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned  (Michael Paquier <michael@paquier.xyz>)
List 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



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Next
From: Shubham Gholap
Date:
Subject: Bug in postgresql related column level security authentication.