Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: d(dot)aumueller(at)proventa(dot)de, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
Date: 2019-11-06 07:41:10
Message-ID: 20191106074110.GJ1604@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Eugen Konkov 2019-11-06 10:15:17 Re: Why 'infinity' is not in range '[2019-01-02, infinity]'?
Previous Message Bruce Momjian 2019-11-06 04:21:11 Re: Why 'infinity' is not in range '[2019-01-02, infinity]'?