Re: Documentation fix on pgbench \aset command - Mailing list pgsql-hackers

From Yugo Nagata
Subject Re: Documentation fix on pgbench \aset command
Date
Msg-id 20250627013148.95b4fddd51e5164484ad358e@sraoss.co.jp
Whole thread Raw
Responses Re: Documentation fix on pgbench \aset command
List pgsql-hackers
On Fri, 27 Jun 2025 01:05:47 +0900
Fujii Masao <masao.fujii@oss.nttdata.com> wrote:

> 
> 
> On 2025/06/26 18:01, Yugo Nagata wrote:
> > Hi,
> > 
> > The current documentation of pgbench’s \aset command states:
> > 
> > “If a query returns no row, no assignment is made and the variable
> >   can be tested for existence to detect this.”
> > 
> > However, this is inaccurate, since variable existence check (like \if :{?var})
> > is not yet supported, although such a feature was proposed in [1] and discussed
> > again in [2], where \aset itself was introduced.
> 
> Right.
> 
> 
> > Therefore, I’ve attached a patch to remove this part from the documentation.
> 
> Or would it be worth documenting an alternative way to detect when no rows are
> returned? For example:
> 
>      If a query returns no rows, no variables are assigned. You can detect
>      this by setting an initial value to the variable before running the query
>      and checking whether it changes.

That's what I thought as well, but I didn’t do it because we can’t distinguish it
from the case where the query returns the same value as the initial one.

To detect it correctly, we would need to reconsider the variable existence check,
or introduce a new meta-command or a special variable that indicates the number of
rows returned by the previous query, and so on.

Regards,
Yugo Nagata


-- 
Yugo Nagata <nagata@sraoss.co.jp>



pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: pg_dump misses comments on NOT NULL constraints
Next
From: Álvaro Herrera
Date:
Subject: Re: queryId constant squashing does not support prepared statements