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

From PG Bug reporting form
Subject BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Date
Msg-id 18134-87126d90cb4dd049@postgresql.org
Whole thread Raw
Responses Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      18134
Logged by:          amutu
Email address:      amutu@amutu.com
PostgreSQL version: 15.4
Operating system:   FreeBSD 13.2-RELEASE amd64
Description:

reproduce steps:

$psql postgres
psql (15.4)
Type "help" for help.

postgres=# select * from cmdq  where status= 'new' \gset
no rows returned for \gset
postgres=# \echo :ROW_COUNT
:ROW_COUNT
postgres=# select * from cmdq;
   cmd   |  src_ip   | worker | status |              ts               | id

---------+-----------+--------+--------+-------------------------------+----
 ls /tmp | 127.0.0.1 |        | done   | 2023-09-23 14:39:59.047309+08 |
1
(1 row)

postgres=# \echo :ROW_COUNT
1
postgres=# select * from cmdq  where status= 'new' \gset
no rows returned for \gset
postgres=# \echo :ROW_COUNT
1
------------------------------------------------
from the psql doc:
ROW_COUNT
The number of rows returned or affected by the last SQL query, !!!!or 0 if
the query failed or did not report a row count.!!!!


pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #17928: Standby fails to decode WAL on termination of primary
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25