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

From Michael Paquier
Subject Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Date
Msg-id ZRjDPucJiWKDJnkf@paquier.xyz
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  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses 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>)
List pgsql-bugs
On Sat, Sep 30, 2023 at 08:44:07PM -0400, Tom Lane wrote:
> Bigger-picture question: should we back-patch this, or just fix it in
> HEAD?  It's wrong, but I'm not sure it's so obviously wrong that there
> could not be somebody depending on the existing behavior.

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.)
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Next
From: Tom Lane
Date:
Subject: Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned