github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-22 22:56:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Update README

Browse Source
This commit is contained in:
Ian Barwick
2017-09-22 13:36:03 +09:00
parent ccdc0a51e9
commit 95cc403efb
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -788,7 +788,7 @@ avoided.
### Separate replication user
In some circumstances it might be desirable to create a dedicated replication-only
user (in addition to the user who manages the `repmgr` metadata. In this case,
user (in addition to the user who manages the `repmgr` metadata). In this case,
the replication user should be set in `repmgr.conf` via the parameter
`replication_user`; `repmgr` will use this value when making replication connections
and generating `recovery.conf`. This value will also be stored in the `repmgr.nodes`
@@ -1670,6 +1670,16 @@ The following commands are available:
replication, just removes the standby's entry from the `repmgr.nodes` table.
See also section "Unregistering a standby from a replication cluster".
* `standby follow`
Attaches the standby to a new primary. This command requires a valid
`repmgr.conf` file for the standby, either specified explicitly with
`-f/--config-file` or located in the current working directory; no
additional arguments are required.
This command will force a restart of the standby server. It can only be used
to attach a standby to a new primary node.
* `standby switchover`
Promotes a standby to primary and demotes the existing primary to a standby.