Re: Inaccuracy in wal_receiver_status_interval parameter description
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Dmitriy Kuzmin <kuzmin.db4@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Date: 2021-02-21T06:58:59Z
Lists: pgsql-docs
Attachments
- replay-status-docs.patch (text/x-diff) patch
On Sat, Feb 20, 2021 at 07:49:21PM +1000, Dmitriy Kuzmin wrote: > I suppose it could be something like this: > "...Setting this parameter to zero disables status updates on a scheduled > basis completely. However there are certain conditions when updates are > still being sent. For example when startup process completes processing WAL > files or when standby is in synchronous mode and synchronous_commit is set > to remote_apply. This parameter can only be set in the postgresql.conf file > or on the server command line." That's an idea. While looking at that I found confusing that the sentence "Setting this parameter to zero disables status updates completely" was completely separate of the rest, where it sounds like even forced messages are disabled if the parameter value is zero, but I think that we should outline that this only applies to the scheduled replies. Attached is what I get. What do you think? -- Michael
Commits
-
doc: Improve description of wal_receiver_status_interval
- c82d59d64e12 14.0 landed