From 6602a98f2ef94d1690896386ebc8e49816c9c675 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Thu, 26 May 2022 10:17:32 +0900 Subject: [PATCH] doc: clarifications for upgrade process --- doc/upgrading-repmgr.xml | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/doc/upgrading-repmgr.xml b/doc/upgrading-repmgr.xml index adf489df..889df99c 100644 --- a/doc/upgrading-repmgr.xml +++ b/doc/upgrading-repmgr.xml @@ -71,6 +71,12 @@ minor release + + A minor release upgrade involves updating &repmgr; from one minor release to another + minor release within the same major release (e.g. 5.3.1 to 5.3.2). + An upgrade between minor releases of differing major releases (e.g. 5.2.1 to 5.3.2) + is a major upgrade. + The process for installing minor version upgrades is quite straightforward: @@ -105,15 +111,17 @@ - A PostgreSQL restart is not required for minor version upgrades. + A PostgreSQL restart is usually not required for minor version upgrades + within the same major version (e.g. 5.3.1 to 5.3.2). + Be sure to check the release notes. - The same &repmgr; "major version" (e.g. 4.2) must be - installed on all nodes in the replication cluster. While it's possible to have differing - &repmgr; "minor versions" (e.g. 4.2.1) on different nodes, - we strongly recommend updating all nodes to the latest minor version. + The same &repmgr; "major version" (e.g. 5.3) must be + installed on all nodes in the replication cluster. While it's possible to have differing + &repmgr; "minor versions" (e.g. 5.3.1 and 5.3.2) + on different nodes, we strongly recommend updating all nodes to the latest minor version.