From 24d7f7227effc5333ab93b930a80c0e61683840a Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Wed, 23 Jan 2019 12:33:05 +0900 Subject: [PATCH] doc: clarify use-cases for pausing repmgrd --- doc/repmgrd-pausing.sgml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/doc/repmgrd-pausing.sgml b/doc/repmgrd-pausing.sgml index 07bb905c..b24a3624 100644 --- a/doc/repmgrd-pausing.sgml +++ b/doc/repmgrd-pausing.sgml @@ -21,13 +21,14 @@ However, repmgrd is unable to distinguish between planned outages (such as performing a switchover - or upgrading a server), and an actual server outage. In versions prior to &repmgr; 4.2 - it was necessary to stop repmgrd on all nodes (or at least + or installing PostgreSQL maintenance released), and an actual server outage. In versions prior to + &repmgr; 4.2 it was necessary to stop repmgrd on all nodes (or at least on all nodes where repmgrd is configured for automatic failover) - to prevent repmgrd from making changes to the + to prevent repmgrd from making unintentional changes to the replication cluster. + From &repmgr; 4.2, repmgrd can now be "paused", i.e. instructed not to take any action such as performing a failover. @@ -35,6 +36,14 @@ each repmgrd individually. + + + For major PostgreSQL upgrades, e.g. from PostgreSQL 10 to PostgreSQL 11, + repmgrd should be shut down completely and only started up + once the &repmgr; packages for the new PostgreSQL major version have been installed. + + + Prerequisites for pausing <application>repmgrd</application>