Re: psql \watch 2nd argument: iteration count - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: psql \watch 2nd argument: iteration count
Date
Msg-id ZBJo0xasYBqrL4Vy@paquier.xyz
Whole thread Raw
In response to Re: psql \watch 2nd argument: iteration count  (Michael Paquier <michael@paquier.xyz>)
Responses Re: psql \watch 2nd argument: iteration count  (Andrey Borodin <amborodin86@gmail.com>)
List pgsql-hackers
On Wed, Mar 15, 2023 at 04:58:49PM +0900, Michael Paquier wrote:
> Yep.  You are right.

Fixed that and applied 0001.

+    valptr++;
+    if (strncmp("i", opt, strlen("i")) == 0 ||
+            strncmp("interval", opt, strlen("interval")) == 0)
+    {

Did you look at process_command_g_options() and if some consolidation
was possible?  It would be nice to have APIs shaped so as more
sub-commands could rely on the same facility in the future.

-        <term><literal>\watch [ <replaceable class="parameter">seconds</replaceable> ]</literal></term>
+        <term><literal>\watch [ <replaceable class="parameter">seconds</replaceable> [ <replaceable
class="parameter">iterations</replaceable>] ]</literal></term>
 

This set of changes is not reflected in the documentation.

With an interval in place, we could now automate some tests with
\watch where it does not fail.  What do you think about adding a test
with a simple query, an interval of 0s and one iteration?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add a hook to allow modification of the ldapbindpasswd
Next
From: Melanie Plageman
Date:
Subject: Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode