Re: wal_sender_timeout / wal_receiver_timeout - seconds ormilliseconds? - Mailing list pgsql-docs

From Michael Paquier
Subject Re: wal_sender_timeout / wal_receiver_timeout - seconds ormilliseconds?
Date
Msg-id 20191106074110.GJ1604@paquier.xyz
Whole thread Raw
In response to Re: wal_sender_timeout / wal_receiver_timeout - seconds ormilliseconds?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: wal_sender_timeout / wal_receiver_timeout - seconds ormilliseconds?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-docs
On Tue, Nov 05, 2019 at 10:21:38AM -0500, Bruce Momjian wrote:
> Ugh, the "if no unit specified" is true of all the settings.  Should we
> make that clearer in a more central location.

Hmm.  Are you thinking about a new single location in the docs?  I
would be afraid to have something like that rot easily as users would
most likely only read the description of each individual parameter
rather than travel across multiple sections.  Also, if you look at
guc.c the default units of each parameter are a case-by-case.
log_rotation_age uses minutes for example, autovacuum_naptime seconds,
etc.
--
Michael

Attachment

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Why 'infinity' is not in range '[2019-01-02, infinity]'?
Next
From: Eugen Konkov
Date:
Subject: Re: Why 'infinity' is not in range '[2019-01-02, infinity]'?