Re: psql \watch 2nd argument: iteration count

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrey Borodin <amborodin86(at)gmail(dot)com>
Cc: Kirk Wolak <wolakk(at)gmail(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Michael Paquier <michael(at)paquier(dot)xyz>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, sfrost(at)snowman(dot)net, peter(dot)eisentraut(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org, samokhvalov(at)gmail(dot)com
Subject: Re: psql \watch 2nd argument: iteration count
Date: 2023-04-06 17:22:58
Message-ID: 2476490.1680801778@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kirk Wolak <wolakk(at)gmail(dot)com> writes:
> Marked as Ready for Committer.

Pushed with a pretty fair number of cosmetic changes.

One non-cosmetic change I made is that I didn't agree with your
interpretation of the execution count. IMO this ought to produce
three executions:

regression=# select 1 \watch c=3
Thu Apr 6 13:17:50 2023 (every 2s)

?column?
----------
1
(1 row)

Thu Apr 6 13:17:52 2023 (every 2s)

?column?
----------
1
(1 row)

Thu Apr 6 13:17:54 2023 (every 2s)

?column?
----------
1
(1 row)

regression=#

If you write a semicolon first, you get four, but it's the semicolon
producing the first result not \watch.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2023-04-06 17:28:49 Re: Schema variables - new implementation for Postgres 15
Previous Message Melanie Plageman 2023-04-06 17:20:56 Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode