From 275fe7ecab25ee17ae9389167e161d60a5da6b41 Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Mon, 19 Sep 2016 13:38:21 -0400
Subject: [PATCH] Update recovery_min_apply_delay docs for remote_apply mode.

Bernd Helmle, reviewed by Thomas Munro, tweaked by me.
---
 doc/src/sgml/recovery-config.sgml | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml
index 26af221745..4a5375ed59 100644
--- a/doc/src/sgml/recovery-config.sgml
+++ b/doc/src/sgml/recovery-config.sgml
@@ -469,10 +469,17 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"'  # Windows
        <para>
         This parameter is intended for use with streaming replication deployments;
         however, if the parameter is specified it will be honored in all cases.
-        Synchronous replication is not affected by this setting because there is
-        not yet any setting to request synchronous apply of transaction commits.
+
         <varname>hot_standby_feedback</> will be delayed by use of this feature
         which could lead to bloat on the master; use both together with care.
+
+        <warning>
+         <para>
+          Synchronous replication is affected by this setting when <varname>synchronous_commit</varname>
+          is set to <literal>remote_apply</literal>; every <literal>COMMIT</literal>
+          will need to wait to be applied.
+         </para>
+        </warning>
        </para>
       </listitem>
      </varlistentry>
-- 
2.40.0