github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-25 08:06:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

doc: update FAQ

Browse Source 
Additional clarification for "repmgr standby clone --recovery-conf-only"
This commit is contained in:
Ian Barwick
2018-03-08 10:02:16 +09:00
committed by Ian Barwick
parent 6f5cce7e6f
commit ff0ba3e19a
2 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
doc/appendix-faq.sgml
View File

@@ -97,7 +97,7 @@
<sect1 id="faq-repmgr" xreflabel="repmgr"> <sect1 id="faq-repmgr" xreflabel="repmgr">
<title><command>repmgr</command></title> <title><command>repmgr</command></title>
<sect2 id="faq-register-existing-node" xreflabel=""> <sect2 id="faq-register-existing-node" xreflabel="registering an existing node">
<title>Can I register an existing PostgreSQL server with repmgr?</title> <title>Can I register an existing PostgreSQL server with repmgr?</title>
<para> <para>
Yes, any existing PostgreSQL server which is part of the same replication Yes, any existing PostgreSQL server which is part of the same replication
@@ -105,6 +105,18 @@
standby to have been cloned using &repmgr;. standby to have been cloned using &repmgr;.
</para> </para>
</sect2> </sect2>
<sect2 id="faq-repmgr-clone-other-source" >
<title>Can I use a standby not cloned by &repmgr; as a &repmgr; node?</title>
<para>
For a standby which has been manually cloned or recovered from an external
backup manager such as Barman, the command
<command><link linkend="repmgr-standby-clone">repmgr standby clone --recovery-conf-only</link></command>
can be used to create the correct <filename>recovery.conf</filename> file for
use with &repmgr; (and will create a replication slot if required). Once this has been done,
<link linkend="repmgr-standby-register">register the node</link> as usual.
</para>
</sect2>
<sect2 id="faq-repmgr-failed-primary-standby" xreflabel="Reintegrate a failed primary as a standby"> <sect2 id="faq-repmgr-failed-primary-standby" xreflabel="Reintegrate a failed primary as a standby">
<title>How can a failed primary be re-added as a standby?</title> <title>How can a failed primary be re-added as a standby?</title>
@@ -203,14 +215,7 @@
</para> </para>
</sect2> </sect2>
<sect2 id="faq-repmgr-clone-other-source" >
<title>Can I use a standby not cloned by &repmgr; as a &repmgr; node?</title>
<para>
Yes - use <link linkend="repmgr-standby-create-recovery-conf">repmgr standby clone --recovery-conf-only</link> to create the node's
<filename>recovery.conf</filename> file, and
<link linkend="repmgr-standby-register">register the node</link> as usual.
</para>
</sect2>
</sect1> </sect1>

2
doc/appendix-release-notes.sgml
View File

@@ -38,7 +38,7 @@
<listitem> <listitem>
<para> <para>
add <command><link linkend="repmgr-standby-clone">repmgr standby clone</link> --recovery-conf-only</command> add <command><link linkend="repmgr-standby-clone">repmgr standby clone --recovery-conf-only</link></command>
option to enable integration of a standby cloned from another source into a &repmgr; cluster (GitHub #382) option to enable integration of a standby cloned from another source into a &repmgr; cluster (GitHub #382)
</para> </para>
</listitem> </listitem>