From: Michael Paquier <michael@paquier.xyz>
To: kuzmin.db4@gmail.com
To: pgsql-docs@lists.postgresql.org
Subject: Re: Inaccuracy in wal_receiver_status_interval parameter description
Date: Wed, 17 Feb 2021 15:01:18 +0900
Message-ID: <YCyxLhg2ZHk0P9rA@paquier.xyz> (raw)
In-Reply-To: <161346024420.3455.1345266601055047937@wrigleys.postgresql.org>
References: <161346024420.3455.1345266601055047937@wrigleys.postgresql.org>
On Tue, Feb 16, 2021 at 07:24:04AM +0000, PG Doc comments form wrote:
> The documentation says that setting wal_receiver_status_interval to 0
> disable updates of replication status completely. However walreceiver keep
> sending status in some cases. For example, when startup has finished
> processing WALs and start waiting for more:
> https://github.com/postgres/postgres/blob/master/src/backend/access/transam/xlog.c#L12598-L12609
> It would be helpful to document in what cases status updates are still being
> sent.
The docs say only that:
"Updates are sent each time the write or flush positions change, or at
least as often as specified by this parameter."
So it could make sense to complete a bit this paragraph with some
words about the places where WalRcvForceReply() or similar logic is
used. The case of the end of the WAL stream ending would be an extra
one. How would you formulate that and what are the cases you think
would be worth mentioning?
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: michael@paquier.xyz, kuzmin.db4@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Inaccuracy in wal_receiver_status_interval parameter description
In-Reply-To: <YCyxLhg2ZHk0P9rA@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox