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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-02 02:27:45
Message-ID: ZRoqoSCbWYxM7_2W@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Sep 30, 2023 at 08:58:12PM -0400, Tom Lane wrote:
> I'm content to wait a day and see if anybody wants to make an
> argument for back-patching.

Okay. Seeing nothing, I've looked more at that this morning and
applied the change to HEAD, for now.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-10-02 02:56:35 Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
Previous Message Tom Lane 2023-10-01 19:45:55 Re: BUG #18141: sorry, too many clients error occurring very frequently