Re: Inaccuracy in wal_receiver_status_interval parameter description

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dmitriy Kuzmin <kuzmin(dot)db4(at)gmail(dot)com>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Inaccuracy in wal_receiver_status_interval parameter description
Date: 2021-02-21 06:58:59
Message-ID: YDIEs5X7C0RJKE2v@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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

Attachment Content-Type Size
replay-status-docs.patch text/x-diff 1.7 KB

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Vik Fearing 2021-02-21 12:52:24 GROUP BY DISTINCT
Previous Message Dmitriy Kuzmin 2021-02-20 09:49:21 Re: Inaccuracy in wal_receiver_status_interval parameter description