github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-23 07:06:30 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

README: clarify that the repmgr metadatabase must be part of the replication cluster

Browse Source
This commit is contained in:
Ian Barwick
2016-10-26 20:28:22 +09:00
parent d4b8c034e9
commit 54a4d1e444
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -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