From bea4b03cc2607dfd025b2853435c1748a7d507e8 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Fri, 14 Sep 2018 14:08:34 +0900 Subject: [PATCH] doc: update "repmgr node rejoin" documentation Clarify various points related to --force-rewind and pg_rewind usage. --- doc/repmgr-node-rejoin.sgml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/doc/repmgr-node-rejoin.sgml b/doc/repmgr-node-rejoin.sgml index b9c6a326..c32285aa 100644 --- a/doc/repmgr-node-rejoin.sgml +++ b/doc/repmgr-node-rejoin.sgml @@ -67,10 +67,10 @@ - Execute pg_rewind if necessary. + Execute pg_rewind. - It is only necessary to provide the pg_rewind + It is only necessary to provide the pg_rewind path if using PostgreSQL 9.3 or 9.4, and pg_rewind is not installed in the PostgreSQL bin directory. @@ -193,7 +193,7 @@ - To have repmgr node rejoin use pg_rewind if required, + To have repmgr node rejoin use pg_rewind, pass the command line option --force-rewind, which will tell &repmgr; to execute pg_rewind to ensure the node can be rejoined successfully. @@ -226,6 +226,15 @@ INFO: pg_rewind would now be executed DETAIL: pg_rewind command is: pg_rewind -D '/var/lib/postgresql/data' --source-server='host=node1 dbname=repmgr user=repmgr' + + + + If is used with the option, + this checks the prerequisites for using pg_rewind, but cannot + predict the outcome of actually executing pg_rewind. + + + $ repmgr node rejoin -f /etc/repmgr.conf -d 'host=node1 dbname=repmgr user=repmgr' \ --force-rewind --config-files=postgresql.local.conf,postgresql.conf --verbose