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

From Bruce Momjian
Subject Re: wal_sender_timeout / wal_receiver_timeout - seconds ormilliseconds?
Date
Msg-id 20191107223617.GC487@momjian.us
Whole thread Raw
In response to Re: wal_sender_timeout / wal_receiver_timeout - seconds ormilliseconds?  (Michael Paquier <michael@paquier.xyz>)
Responses Re: wal_sender_timeout / wal_receiver_timeout - seconds ormilliseconds?
List pgsql-docs
On Wed, Nov  6, 2019 at 04:41:10PM +0900, Michael Paquier wrote:
> 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.

Right.  I am just asking if we need to do this for _every_ case where
the default value doesn't match the default _units_, or if we need to
have some kind of central notification.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-docs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: The word "virgin" used incorrectly and probably better offreplaced
Next
From: Bruce Momjian
Date:
Subject: Re: The word "virgin" used incorrectly and probably better offreplaced