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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Japin Li <japinli(at)hotmail(dot)com>, amutu(at)amutu(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Date: 2023-10-01 00:58:12
Message-ID: 1617077.1696121892@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Shubham Gholap 2023-10-01 07:59:17 Bug in postgresql related column level security authentication.
Previous Message Michael Paquier 2023-10-01 00:54:22 Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned