From cb61b447f38148ffd6c7dc02aad145e5c367f0a1 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Fri, 22 Sep 2017 17:40:14 +0900 Subject: [PATCH] Document "repmgr standby unregister" --- doc/command-reference.sgml | 30 ++++++++++++++++++++++++++++++ doc/repmgr.sgml | 1 + 2 files changed, 31 insertions(+) diff --git a/doc/command-reference.sgml b/doc/command-reference.sgml index 6fb419f9..a7814160 100644 --- a/doc/command-reference.sgml +++ b/doc/command-reference.sgml @@ -148,6 +148,36 @@ + + + repmgr standby unregister + repmgr standby unregister + + Unregisters a standby with `repmgr`. This command does not affect the actual + replication, just removes the standby's entry from the &repmgr; metadata. + + + To unregister a running standby, execute: + + repmgr standby unregister -f /etc/repmgr.conf + + + This will remove the standby record from &repmgr;'s internal metadata + table (repmgr.nodes). A standby_unregister + event notification will be recorded in the repmgr.events table. + + + If the standby is not running, the command can be executed on another + node by providing the id of the node to be unregistered using + the command line parameter --node-id, e.g. executing the following + command on the master server will unregister the standby with + id 3: + + repmgr standby unregister -f /etc/repmgr.conf --node-id=3 + + + + repmgr standby promote diff --git a/doc/repmgr.sgml b/doc/repmgr.sgml index a6b17330..dd9aee03 100644 --- a/doc/repmgr.sgml +++ b/doc/repmgr.sgml @@ -70,6 +70,7 @@ &configuration; &cloning-standbys; &promoting-standby; + &follow-new-primary; &command-reference;