From cf9c45bc26e7a4332c7285a17ee9c4396dc8042d Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Wed, 29 Jan 2014 20:27:37 -0500
Subject: [PATCH] Document hazards of --slot.

---
 doc/src/sgml/ref/pg_receivexlog.sgml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/src/sgml/ref/pg_receivexlog.sgml b/doc/src/sgml/ref/pg_receivexlog.sgml
index e592699ac7..2a44af46c5 100644
--- a/doc/src/sgml/ref/pg_receivexlog.sgml
+++ b/doc/src/sgml/ref/pg_receivexlog.sgml
@@ -232,6 +232,14 @@ PostgreSQL documentation
         <para>
          Require <application>pg_receivexlog</application> to use an existing
          replication slot (see <xref linkend="streaming-replication-slots">).
+         When this option is used, <application>pg_receivexlog</> will report
+         a flush position to the server, indicating when each segment has been
+         synchronized to disk so that the server can remove that segment if it
+         is not otherwise needed.  When using this paramter, it is important
+         to make sure that <application>pg_receivexlog</> cannot become the
+         synchronous standby through an incautious setting of
+         <xref linkend="guc-synchronous-standby-names">; it does not flush
+         data frequently enough for this to work correctly.
         </para>
       </listitem>
      </varlistentry>
-- 
2.39.5