Date: Mon, 4 Nov 2019 21:52:34 -0500
From: Bruce Momjian <bruce@momjian.us>
To: d.aumueller@proventa.de, pgsql-docs@lists.postgresql.org
Subject: Re: wal_sender_timeout / wal_receiver_timeout - seconds or
 milliseconds?
Message-ID: <20191105025234.GC12780@momjian.us>
References: <157192240500.1043.7917781375772404449@wrigleys.postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <157192240500.1043.7917781375772404449@wrigleys.postgresql.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Thu, Oct 24, 2019 at 01:06:45PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/12/runtime-config-replication.html
> Description:
> 
> Dear sir or madam!
> 
> The documentation about the parameter wal_sender_timeout refers to an
> integer value in milliseconds in the first sentence. Reading up to the
> default value in the paragraph, it is set to 60 seconds. The same difference
> of milliseconds and seconds is included in postgresql.conf:
> 
> #wal_sender_timeout = 60s       # in milliseconds; 0 disables
> 
> This difference is found in the documentation and postgresql.conf for
> parameter wal_receiver_timeout, too.
> 
> #wal_receiver_timeout = 60s             # time that receiver waits for
>                                         # communication from master
>                                         # in milliseconds; 0 disables
> 
> Please check and verify. - Thank you!

The default _value_ is 60 seconds, and we use the 's' to specify
seconds.  What the comment is saying is that if you _don't_ specify any
units, the integer is in milliseconds.  I am not sure how to improve
that.

-- 
  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 +