From 54a4d1e444c66c7022154cb16763530560b9cf94 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Wed, 26 Oct 2016 20:28:22 +0900 Subject: [PATCH] README: clarify that the repmgr metadatabase must be part of the replication cluster --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 31149909..d57184e1 100644 --- a/README.md +++ b/README.md @@ -121,7 +121,8 @@ views: status for each node The `repmgr` metadata schema can be stored in an existing database or in its own -dedicated database. +dedicated database. Note that the `repmgr` metadata schema cannot reside on a database +server which is not part of the replication cluster managed by `repmgr`. A dedicated database superuser is required to own the meta-database as well as carry out administrative actions. @@ -1072,8 +1073,9 @@ This will remove the standby record from `repmgr`'s internal metadata table (`repl_nodes`). A `standby_unregister` event notification will be recorded in the `repl_events` table. -Note that this command will not stop the server itself or remove -it from the replication cluster. +Note that this command will not stop the server itself or remove it from +the replication cluster. Note that if the standby was using a replication +slot, this will not be removed. 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