diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml
index 9628458b..6f39b651 100644
--- a/doc/appendix-release-notes.sgml
+++ b/doc/appendix-release-notes.sgml
@@ -23,14 +23,34 @@
behaviour and some additional configuration parameters.
- &repmgr; 4.1.0 introduces changes to the &repmgr; extension schema, meaning
- ALTER EXTENSION repmgr UPGRADE must be executed after
- installing the new version.
+ This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.0.6.
+ The following post-upgrade steps must be carried out:
+
+
+
+
+ repmgrd (if running) must be restarted.
+
+
+
+
+ Execute ALTER EXTENSION repmgr UPGRADE
+ on the primary server in the database where &repmgr; is installed.
+
+
+
+
+ A restart of the PostgreSQL server is not required
+ for this release.
+
+ See for more details.
+
+
Configuration changes are backwards-compatible and no changes to
repmgr.conf are required. However users should
- review changes listed below.
+ review the changes listed below.
diff --git a/doc/upgrading-repmgr.sgml b/doc/upgrading-repmgr.sgml
index 0208db09..74b4eb0e 100644
--- a/doc/upgrading-repmgr.sgml
+++ b/doc/upgrading-repmgr.sgml
@@ -29,8 +29,18 @@
- In the database where the &repmgr; extension is installed, execute
- ALTER EXTENSION repmgr UPDATE.
+ repmgrd (if running) must be restarted.
+
+
+
+
+ For major releases, e.g. from 4.0.x to 4.1,
+ execute ALTER EXTENSION repmgr UPDATE
+ on the primary node in the database where the &repmgr; extension is installed.
+
+
+ This will update the extension metadata and, if necessary, apply
+ changes to the &repmgr; extension objects.
@@ -41,10 +51,6 @@
release as they may contain upgrade instructions particular to individual versions.
-
- If the repmgrd daemon is in use, we recommend stopping it
- before upgrading &repmgr;.
-
Note that it may be necessary to restart the PostgreSQL server if the upgrade contains
changes to the shared object file used by repmgrd; check the