From 95cc403efbf9fd104181f2ca95f1899844c36456 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Fri, 22 Sep 2017 13:36:03 +0900 Subject: [PATCH] Update README --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 61657a0e..5412be98 100644 --- a/README.md +++ b/README.md @@ -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.