Re: pg_receivewal documentation

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: jesper.pedersen@redhat.com, Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-07-18T05:29:09Z
Lists: pgsql-hackers
On Wed, Jul 17, 2019 at 11:21:06PM +0200, Laurenz Albe wrote:
> Ok, here's another attempt:
> 
>    Note that while WAL will be flushed with this setting,
>    <application>pg_receivewal</application> never applies it, so
>    <xref linkend="guc-synchronous-commit"/> must not be set to
>    <literal>remote_apply</literal> if <application>pg_receivewal</application>
>    is the only synchronous standby.
>    Similarly, it is no use adding <application>pg_receivewal</application> to a
>    priority-based (<literal>FIRST</literal>) or a quorum-based
>    (<literal>ANY</literal>) synchronous replication setup if
>    <xref linkend="guc-synchronous-commit"/> is set to <literal>remote_apply</literal>.

Or more simply like that?
"Note that while WAL will be flushed with this setting,
pg_receivewal never applies it, so synchronous_commit must not be set
to remote_apply if pg_receivewal is a synchronous standby, be it a
member of a priority-based (FIRST) or a quorum-based (ANY) synchronous
replication setup."
--
Michael

Commits

  1. Doc: Clarify interactions of pg_receivexlog with remote_apply

  2. Doc: Clarify interactions of pg_receivewal with remote_apply