diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml
index e0cb1cc6..b2e9f979 100644
--- a/doc/appendix-release-notes.sgml
+++ b/doc/appendix-release-notes.sgml
@@ -175,11 +175,18 @@ REPMGRD_OPTS="--daemonize=false"
- New configuration option
+ New configuration option
to allow an external mechanism to validate the failover decision made by repmgrd.
+
+
+ New configuration option
+ to force standbys to disconnect their WAL receivers before making a failover decision.
+
+
+
diff --git a/doc/repmgrd-automatic-failover.sgml b/doc/repmgrd-automatic-failover.sgml
index d15ace54..c591971a 100644
--- a/doc/repmgrd-automatic-failover.sgml
+++ b/doc/repmgrd-automatic-failover.sgml
@@ -110,6 +110,53 @@
+
+
+ repmgrd
+ standby disconnection on failover
+
+
+
+ standby disconnection on failover
+
+
+ Standby disconnection on failover
+
+ If is set to true in
+ repmgr.conf, in a failover situation repmgrd will forcibly disconnect
+ the local node's WAL receiver before making a failover decision.
+
+
+
+ is available from PostgreSQL 9.5 and later.
+ Additionally this requires that the repmgr database user is a superuser.
+
+
+
+ By doing this, it's possible to ensure that, at the point the failover decision is made, no nodes
+ are receiving data from the primary and their LSN location will be static.
+
+
+
+ must be set to the same value on
+ all nodes.
+
+
+
+ Note that when using there will be a delay of 5 seconds
+ plus however many seconds it takes to confirm the WAL receiver is disconnected before
+ repmgrd proceeds with the failover decision.
+
+
+ Following the failover operation, no matter what the outcome, each node will reconnect its WAL receiver.
+
+
+ If using , we recommend that the
+ option is also used.
+
+
+
+
repmgrd
diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml
index aa40606d..bb70301d 100644
--- a/doc/repmgrd-configuration.sgml
+++ b/doc/repmgrd-configuration.sgml
@@ -406,6 +406,9 @@
+
+ See also: Standby disconnection on failover.
+