summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2016-09-19 13:38:21 -0400
committerRobert Haas <rhaas@postgresql.org>2016-09-19 13:40:25 -0400
commit275fe7ecab25ee17ae9389167e161d60a5da6b41 (patch)
tree5954d2a7fce65b204f3652bb80436038395f761f
parente06728d631a6bb511006d7e85839713abcdbb555 (diff)
Update recovery_min_apply_delay docs for remote_apply mode.
Bernd Helmle, reviewed by Thomas Munro, tweaked by me.
-rw-r--r--doc/src/sgml/recovery-config.sgml11
1 files changed, 9 insertions, 2 deletions
diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml
index 26af221745c..4a5375ed593 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>