From ea653a8dbc6b1bd7495cb37e02d7371e63a09318 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Fri, 2 Feb 2018 15:42:08 +0900
Subject: [PATCH] "standby follow": finalize implementation of --dry-run option

---
 HISTORY                        | 1 +
 doc/repmgr-standby-follow.sgml | 8 ++++++++
 2 files changed, 9 insertions(+)

diff --git a/HISTORY b/HISTORY
index d5039b8c..c34e9f05 100644
--- a/HISTORY
+++ b/HISTORY
@@ -3,6 +3,7 @@
           server and logging output is not explicitly redirected (Ian)
         repmgr: improve switchover log messages and exit code when old primary could
           not be shut down cleanly (Ian)
+        repmgr: add --dry-run mode to "repmgr standby follow"; GitHub #368 (Ian)
 
 4.0.2   2018-01-18
         repmgr: add missing -W option to getopt_long() invocation; GitHub #350 (Ian)
diff --git a/doc/repmgr-standby-follow.sgml b/doc/repmgr-standby-follow.sgml
index 2c6104ad..1bee915b 100644
--- a/doc/repmgr-standby-follow.sgml
+++ b/doc/repmgr-standby-follow.sgml
@@ -58,6 +58,14 @@
           <para>
             Check prerequisites but don't actually follow a new standby.
           </para>
+          <important>
+            <para>
+              This does not guarantee the standby can follow the primary; in
+              particular, whether the primary and standby timelines have diverged,
+              can currently only be determined by actually attempting to
+              attach the standby to the primary.
+            </para>
+          </important>
         </listitem>
       </varlistentry>