From: Euler Taveira <euler@eulerto.com>
To: Michael Paquier <michael@paquier.xyz>
To: Dmitriy Kuzmin <kuzmin.db4@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Inaccuracy in wal_receiver_status_interval parameter description
Date: Sun, 21 Feb 2021 21:21:41 -0300
Message-ID: <0c781819-bda3-4ec8-a464-a63c63695ea5@www.fastmail.com> (raw)
In-Reply-To: <YDIEs5X7C0RJKE2v@paquier.xyz>
References: <161346024420.3455.1345266601055047937@wrigleys.postgresql.org>
<YCyxLhg2ZHk0P9rA@paquier.xyz>
<CAHLDt=9iiScn8wkCnFDWc=1Osdnn5XePR=6q+vj6Rne19k8Vrw@mail.gmail.com>
<YDIEs5X7C0RJKE2v@paquier.xyz>
On Sun, Feb 21, 2021, at 3:58 AM, Michael Paquier wrote:
> 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?
LGTM.
--
Euler Taveira
EDB https://www.enterprisedb.com/
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: euler@eulerto.com, 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: <0c781819-bda3-4ec8-a464-a63c63695ea5@www.fastmail.com>
* 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