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: clarify "node rejoin" usage

Browse Source 
Emphasize that conninfo must be provided for a running node.
This commit is contained in:
Ian Barwick
2020-07-06 09:53:23 +09:00
parent 8313944535
commit b9874cd751
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/repmgr-node-rejoin.xml
View File

@@ -43,7 +43,12 @@
<programlisting> <programlisting>
repmgr node rejoin -d '$conninfo'</programlisting> repmgr node rejoin -d '$conninfo'</programlisting>
where <literal>$conninfo</literal> is the conninfo string of any reachable node in the cluster. where <literal>$conninfo</literal> is the PostgreSQL <literal>conninfo</literal> string of the
<emphasis>current</emphasis> primary node (or that of any reachable node in the cluster, but
<emphasis>not</emphasis> the local node). This is so that &repmgr; can fetch up-to-date information
about the current state of the cluster.
</para>
<para>
<filename>repmgr.conf</filename> for the stopped node *must* be supplied explicitly if not <filename>repmgr.conf</filename> for the stopped node *must* be supplied explicitly if not
otherwise available. otherwise available.
</para> </para>