mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-27 17:06:29 +00:00
doc: update "standby follow" reference
Add note about handling of timeline forks etc.
This commit is contained in:
@@ -146,6 +146,39 @@
|
|||||||
</variablelist>
|
</variablelist>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
<refsect1>
|
||||||
|
<title>Execution</title>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Execute with the <literal>--dry-run</literal> option to test the follow operation as
|
||||||
|
far as possible, without actually changing the status of the node.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Note that &repmgr; will first attempt to determine whether the standby
|
||||||
|
("follow candidate") is capable of following the
|
||||||
|
new upstream node ("follow target").
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
If, for example, the new upstream node has diverged from this node's timeline,
|
||||||
|
for example if the new upstream node was promoted to primary while this node
|
||||||
|
was still attached to the original primary, it will <emphasis>not</emphasis>
|
||||||
|
be possible to follow the new upstream node, and &repmgr; will emit an error
|
||||||
|
message like this:
|
||||||
|
<programlisting>
|
||||||
|
ERROR: this node cannot attach to follow target node 3
|
||||||
|
DETAIL: follow target server's timeline 2 forked off current database system timeline 1 before current recovery point 0/6108880</programlisting>
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
In this case, it may be possible to have this node follow the new upstream
|
||||||
|
using <command><link linkend="repmgr-node-rejoin">repmgr node rejoin</link></command>
|
||||||
|
with the <option>--force-rewind</option> to execute <command>pg_rewind</command>.
|
||||||
|
This does mean that transacations which exist on this node, but not the new upstream,
|
||||||
|
will be lost.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Exit codes</title>
|
<title>Exit codes</title>
|
||||||
<para>
|
<para>
|
||||||
@@ -210,7 +243,7 @@
|
|||||||
A <literal>standby_follow</literal> <link linkend="event-notifications">event notification</link> will be generated.
|
A <literal>standby_follow</literal> <link linkend="event-notifications">event notification</link> will be generated.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
If provided, &repmgr; will substitute the placeholders <literal>%p</literal> with the node ID of the primary
|
If provided, &repmgr; will substitute the placeholders <literal>%p</literal> with the node ID of the node
|
||||||
being followed, <literal>%c</literal> with its <literal>conninfo</literal> string, and
|
being followed, <literal>%c</literal> with its <literal>conninfo</literal> string, and
|
||||||
<literal>%a</literal> with its node name.
|
<literal>%a</literal> with its node name.
|
||||||
</para>
|
</para>
|
||||||
|
|||||||
Reference in New Issue
Block a user