diff --git a/doc/appendix-faq.sgml b/doc/appendix-faq.sgml
index 8d3581e0..cf7256a6 100644
--- a/doc/appendix-faq.sgml
+++ b/doc/appendix-faq.sgml
@@ -97,7 +97,7 @@
repmgr
-
+ Can I register an existing PostgreSQL server with repmgr?
Yes, any existing PostgreSQL server which is part of the same replication
@@ -105,6 +105,18 @@
standby to have been cloned using &repmgr;.
+
+ Can I use a standby not cloned by &repmgr; as a &repmgr; node?
+
+
+ For a standby which has been manually cloned or recovered from an external
+ backup manager such as Barman, the command
+ repmgr standby clone --recovery-conf-only
+ can be used to create the correct recovery.conf file for
+ use with &repmgr; (and will create a replication slot if required). Once this has been done,
+ register the node as usual.
+
+ How can a failed primary be re-added as a standby?
@@ -203,14 +215,7 @@
-
- Can I use a standby not cloned by &repmgr; as a &repmgr; node?
-
- Yes - use repmgr standby clone --recovery-conf-only to create the node's
- recovery.conf file, and
- register the node as usual.
-
-
+
diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml
index 08262ce5..02e37fc6 100644
--- a/doc/appendix-release-notes.sgml
+++ b/doc/appendix-release-notes.sgml
@@ -38,7 +38,7 @@
- add repmgr standby clone --recovery-conf-only
+ add repmgr standby clone --recovery-conf-only
option to enable integration of a standby cloned from another source into a &repmgr; cluster (GitHub #382)