Re: Prevent psql \watch from running queries that return no rows

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Prevent psql \watch from running queries that return no rows
Date: 2023-06-03 21:58:46
Message-ID: ZHu3li_s4hS0XW9n@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 02, 2023 at 11:47:16AM -0400, Greg Sabino Mullane wrote:
> * Not completely convinced of the name "zero" (better than
> "stop_when_no_rows_returned"). Considered adding a new x=y argument, or
> overloading c (c=-1) but neither seemed very intuitive. On the other hand,
> it's tempting to stick to a single method moving forward, although this is
> a boolean option not a x=y one like the other two.

Wouldn't something like a target_rows be more flexible? You could use
this parameter with a target number of rows to expect, zero being one
choice in that.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-06-03 22:21:27 Re: Implement generalized sub routine find_in_log for tap test
Previous Message Michael Paquier 2023-06-03 21:50:38 Re: Docs: Encourage strong server verification with SCRAM