Re: Possibly hard-to-read message

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
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-03-27 01:34:06
Message-ID: CAKFQuwbV7kD-v-SYjyQTvxOUui5HkRcXO4RoMNnbPaDL=Bw0WQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 26, 2025 at 2:11 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

> On 26 Mar 2025, at 04:52, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
> wrote:
> On Tue, Mar 25, 2025 at 8:07 PM Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
> wrote:
>
>
> I came across the following help message added in commit 1a759c83278:
>>
>> + HELP0(" WATCH_INTERVAL\n"
>> + " number of seconds \\watch by default waits between
>> executing the query buffer\n");
>>
>> It took me a little while to understand it.
>>
>
> I'm on board with tweaking this.
>
>
> How about the attached? We already have "(default: X)" in other places so
> this
> aligns it better while simplifying the language.
>
>
This change is technically wrong on two points:

I pondered mentioning the 2s interval but the environment variable itself
doesn't have a default, it's either set or unset which determines whether
it provides the default or not. IMO, adding this detail produces too much
text for little benefit.

Your wording loses the idea that this environment variable only establishes
a new default that can be subsequently overridden by explicitly specifying
an interval to \watch.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yurii Rashkovskii 2025-03-27 01:38:50 Re: Add Postgres module info
Previous Message Michael Paquier 2025-03-27 01:21:39 Re: A small correction to doc and comment of FSM for indexes