From bce039f336ead3d6e52bca8006a917e74324d626 Mon Sep 17 00:00:00 2001
From: Ian Barwick <barwick@gmail.com>
Date: Thu, 5 Sep 2019 18:00:56 +0900
Subject: [PATCH] doc: add clarifications to "Standby disconnection on
 failover"

---
 doc/repmgrd-automatic-failover.xml | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/doc/repmgrd-automatic-failover.xml b/doc/repmgrd-automatic-failover.xml
index cb864122..20bc6858 100644
--- a/doc/repmgrd-automatic-failover.xml
+++ b/doc/repmgrd-automatic-failover.xml
@@ -268,11 +268,12 @@
   <para>
     If <option>standby_disconnect_on_failover</option> is set to <literal>true</literal> in
     <filename>repmgr.conf</filename>, in a failover situation &repmgrd; will forcibly disconnect
-    the local node's WAL receiver before making a failover decision.
+    the local node's WAL receiver, and wait for the WAL receiver on all sibling nodes to be
+	disconnected, before making a failover decision.
   </para>
   <note>
     <para>
-      <option>standby_disconnect_on_failover</option> is available from PostgreSQL 9.5 and later.
+      <option>standby_disconnect_on_failover</option> is available with PostgreSQL 9.5 and later.
       Additionally this requires that the <literal>repmgr</literal> database user is a superuser.
     </para>
   </note>
@@ -291,6 +292,12 @@
     plus however many seconds it takes to confirm the WAL receiver is disconnected before
     &repmgrd; proceeds with the failover decision.
   </para>
+  <para>
+	&repmgrd; will wait up to <option>sibling_nodes_disconnect_timeout</option> seconds (default:
+	<literal>30</literal>) to confirm that the WAL receiver on all sibling nodes hase been
+	disconnected before proceding with the failover operation. If the timeout is reached, the
+	failover operation will go ahead anyway.
+  </para>
   <para>
     Following the failover operation, no matter what the outcome, each node will reconnect its WAL receiver.
   </para>