From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | 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-05 02:52:34 |
Message-ID: | 20191105025234.GC12780@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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(at)momjian(dot)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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-11-05 04:27:16 | Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds? |
Previous Message | PG Doc comments form | 2019-11-04 07:11:48 | auto_explain.log_min_duration is limit for nested statement |