From 5c1ca6cba588b0a51260ead4c5e1ef6822fd2062 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Tue, 13 Aug 2019 11:36:15 +0900 Subject: [PATCH] doc: mention not to use --siblings-follow in the repmgrd promote command This is noted on the "repmgr standby promote" page but needs repeating on the repmgrd configuration page. --- doc/repmgr-standby-follow.xml | 2 +- doc/repmgrd-configuration.xml | 11 +++++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/doc/repmgr-standby-follow.xml b/doc/repmgr-standby-follow.xml index b0f4a6b6..cca1e2e1 100644 --- a/doc/repmgr-standby-follow.xml +++ b/doc/repmgr-standby-follow.xml @@ -171,7 +171,7 @@ be possible to follow the new upstream node, and &repmgr; will emit an error message like this: -ERROR: this node cannot attach to follow target node 3 +ERROR: this node cannot attach to follow target node "node3" (ID 3) DETAIL: follow target server's timeline 2 forked off current database system timeline 1 before current recovery point 0/6108880 diff --git a/doc/repmgrd-configuration.xml b/doc/repmgrd-configuration.xml index 62dc5bf5..30379936 100644 --- a/doc/repmgrd-configuration.xml +++ b/doc/repmgrd-configuration.xml @@ -222,6 +222,17 @@ Normally is set as &repmgr;'s repmgr standby promote command. + + + + When invoking repmgr standby promote (either directly via + the , or in a script called + via ), + must not be included as a + command line option for repmgr standby promote. + + + It is also possible to provide a shell script to e.g. perform user-defined tasks before promoting the current node. In this case the script must