mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
43 lines
1.2 KiB
Plaintext
43 lines
1.2 KiB
Plaintext
<refentry id="repmgr-primary-unregister">
|
|
<indexterm>
|
|
<primary>repmgr primary unregister</primary>
|
|
</indexterm>
|
|
<refmeta>
|
|
<refentrytitle>repmgr primary unregister</refentrytitle>
|
|
</refmeta>
|
|
<refnamediv>
|
|
<refname>repmgr primary unregister</refname>
|
|
<refpurpose>unregister an inactive primary node</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
<para>
|
|
<command>repmgr primary register</command> unregisters an inactive primary node
|
|
from the &repmgr; metadata. This is typically when the primary has failed and is
|
|
being removed from the cluster after a new primary has been promoted.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Execution</title>
|
|
<para>
|
|
Execute with the <literal>--dry-run</literal> option to check what would happen without
|
|
actually unregistering the node.
|
|
</para>
|
|
|
|
<para>
|
|
<command>repmgr master unregister</command> can be used as an alias for
|
|
<command>repmgr primary unregister</command>/
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Event notifications</title>
|
|
<para>
|
|
A <literal>primary_unregister</literal> event notification will be generated.
|
|
</para>
|
|
</refsect1>
|
|
|
|
</refentry>
|