From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_receivewal documentation |
Date: | 2019-07-10 14:24:21 |
Message-ID: | 20190710142421.GA28387@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-Jul-09, Jesper Pedersen wrote:
> + <para>
> + Note that while WAL will be flushed with this setting,
> + it will never be applied, 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.
> + </para>
+1 to document this caveat.
How about
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.
?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-07-10 14:32:20 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
Previous Message | Binguo Bao | 2019-07-10 14:18:24 | Re: [proposal] de-TOAST'ing using a iterator |