From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | d(dot)aumueller(at)proventa(dot)de |
Subject: | wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds? |
Date: | 2019-10-24 13:06:45 |
Message-ID: | 157192240500.1043.7917781375772404449@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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!
With best regards,
Dirk Aumueller
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-10-24 14:31:44 | Re: uniqueness and null could benefit from a hint for dba |
Previous Message | Bruce Momjian | 2019-10-24 02:05:44 | Re: PostgreSQL 12 release notes missing breaking change in libpq |