Re: Possibly hard-to-read message

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Possibly hard-to-read message
Date: 2025-04-06 21:52:34
Message-ID: 2E4127D5-85B9-40B5-8D6F-C44B57E92DDD@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 27 Mar 2025, at 02:42, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On second thought, something like:
>
> WATCH_INTERVAL: an integer number of seconds; overrides the default two second \watch interval
>
> (not quite happy but it's close...keeps the 2s reference point)

Looking at the other variables they tend to use "if set, then" so we should
probably stick to that for this as well? Something like the below perhaps?

HELP0(" WATCH_INTERVAL\n"
- " number of seconds \\watch by default waits between executing the query buffer\n");
+ " if set to an interval value, overrides the default two second \\watch interval\n");

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-04-06 22:01:01 Re: Logging which local address was connected to in log_line_prefix
Previous Message Michael Paquier 2025-04-06 21:49:02 Re: [PATCH] clarify palloc comment on quote_literal_cstr