From 37b458dfcdc90612ca028f325d05bb6ba40c8ae6 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Fri, 25 Aug 2017 16:13:38 +0900 Subject: [PATCH] Various documentation updates --- README.md | 7 +++++++ docs/repmgrd-node-fencing.md | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 194d23e6..c4081528 100644 --- a/README.md +++ b/README.md @@ -996,6 +996,13 @@ both passwordless SSH access and the path of `repmgr.conf` on that server. > careful preparation and with adequate attention. In particular you should > be confident that your network environment is stable and reliable. > +> Additionally you should be sure that the current master can be shut down +> quickly and cleanly. In particular, access from applications should be +> minimalized or preferably blocked completely. Also check that there is +> no backlog of files waiting to be archived, as PostgreSQL will not shut +> down until archiving completes, and that any standbys attached to the +> current primary don't have a significant amount of replication lag. +> > We recommend running `repmgr standby switchover` at the most verbose > logging level (`--log-level DEBUG --verbose`) and capturing all output > to assist troubleshooting any problems. diff --git a/docs/repmgrd-node-fencing.md b/docs/repmgrd-node-fencing.md index d08be52e..5f2286fb 100644 --- a/docs/repmgrd-node-fencing.md +++ b/docs/repmgrd-node-fencing.md @@ -133,7 +133,7 @@ The actual script is as follows; adjust the configurable items as appropriate: psql -d $REPMGR_DB -U $REPMGR_USER -t -A \ -c "SELECT '${PGBOUNCER_DATABASE}-ro= ' || conninfo || ' application_name=pgbouncer_${HOST}' \ - FROM $REPMGR_SCHEMA.repl_nodes \ + FROM ${REPMGR_SCHEMA}.repl_nodes \ WHERE node_name='${HOST}'" >> $PGBOUNCER_DATABASE_INI_NEW rsync $PGBOUNCER_DATABASE_INI_NEW $HOST:$PGBOUNCER_DATABASE_INI