diff --git a/doc/appendix-release-notes.xml b/doc/appendix-release-notes.xml
index 68f7290e..87fe5c71 100644
--- a/doc/appendix-release-notes.xml
+++ b/doc/appendix-release-notes.xml
@@ -19,37 +19,37 @@
Release 4.4?? June, 2019
-
+ repmgr client enhancements
-
+
-
+
- repmgr standby clone:
- prevent a standby from being cloned from a witness server (PostgreSQL 9.6 and later only).
-
-
+ repmgr standby clone:
+ prevent a standby from being cloned from a witness server (PostgreSQL 9.6 and later only).
+
+
-
+
- repmgr witness register:
- prevent a witness server from being registered on the replication cluster primary server
+ repmgr witness register:
+ prevent a witness server from being registered on the replication cluster primary server
(PostgreSQL 9.6 and later only).
-
+
Registering a witness on the primary node would defeat the purpose of having a witness server,
which is intended to remain running even if the cluster's primary goes down.
-
+
-
+ repmgr standby follow:
note that an active, reachable cluster primary is required for this command;
- and provide a more helpful error message if no reachable primary could be found.
+ and provide a more helpful error message if no reachable primary could be found.
-
+
@@ -101,61 +101,61 @@
-
+
- repmgr standby switchover:
- add to unpause all &repmgrd; instances after executing a switchover.
- This will ensure that any &repmgrd; instances which were paused before the switchover will be
- unpaused.
-
-
+ repmgr standby switchover:
+ add to unpause all &repmgrd; instances after executing a switchover.
+ This will ensure that any &repmgrd; instances which were paused before the switchover will be
+ unpaused.
+
+ repmgr daemon status:
- make output similar to that of
- repmgr cluster show
- for consistency and to make it easier to identify nodes not in the expected
- state.
+ make output similar to that of
+ repmgr cluster show
+ for consistency and to make it easier to identify nodes not in the expected
+ state.
-
+ repmgr cluster show:
- display each node's timeline ID (PostgreSQL 9.6 and later only).
-
-
-
-
-
- repmgr cluster show
- and repmgr daemon status:
- show the upstream node name as reported by each individual node - this helps visualise
- situations where the cluster is in an unexpected state, and provide a better idea of the
- actual cluster state.
-
-
- For example, if a cluster has divided somehow and a set of nodes are
- following a new primary, when running either of these commands, &repmgr;
- will now show the name of the primary those nodes are actually
- following, rather than the now outdated node name recorded
- on the other side of the "split". A warning will also be issued
- about the unexpected situation.
+ display each node's timeline ID (PostgreSQL 9.6 and later only).
-
+ repmgr cluster show
- and repmgr daemon status:
- check if a node is attached to its advertised upstream node, and issue a
- warning if the node is not attached.
-
-
+ and repmgr daemon status:
+ show the upstream node name as reported by each individual node - this helps visualise
+ situations where the cluster is in an unexpected state, and provide a better idea of the
+ actual cluster state.
+
+
+ For example, if a cluster has divided somehow and a set of nodes are
+ following a new primary, when running either of these commands, &repmgr;
+ will now show the name of the primary those nodes are actually
+ following, rather than the now outdated node name recorded
+ on the other side of the "split". A warning will also be issued
+ about the unexpected situation.
+
+
-
-
+
+
+ repmgr cluster show
+ and repmgr daemon status:
+ check if a node is attached to its advertised upstream node, and issue a
+ warning if the node is not attached.
+
+
+
+
+
@@ -228,21 +228,21 @@
-
-
+
+
&repmgr;: when executing repmgr standby clone
with the , ensure that application_name
is set correctly in primary_conninfo.
-
-
+
+
&repmgr;: when executing repmgr standby switchover,
don't abort if one or more nodes are not reachable and
- they are marked as inactive.
-
-
+ they are marked as inactive.
+
+
@@ -254,15 +254,15 @@
-
-
+
+
&repmgrd;: fix memory leak which occurs while the monitored PostgreSQL node is not
running.
-
+
@@ -306,19 +306,19 @@
-
-
- On Debian-based systems, including Ubuntu, if using &repmgrd;
- please ensure that in the file /etc/init.d/repmgrd, the parameter
- REPMGRD_OPTS contains "--daemonize=false", e.g.:
-
+
+
+ On Debian-based systems, including Ubuntu, if using &repmgrd;
+ please ensure that in the file /etc/init.d/repmgrd, the parameter
+ REPMGRD_OPTS contains "--daemonize=false", e.g.:
+
# additional options
REPMGRD_OPTS="--daemonize=false"
-
-
- For further details, see repmgrd configuration on Debian/Ubuntu.
-
-
+
+
+ For further details, see repmgrd configuration on Debian/Ubuntu.
+
+ repmgr client enhancements
@@ -383,11 +383,11 @@ REPMGRD_OPTS="--daemonize=false"
repmgr cluster show:
- differentiate between unreachable nodes and nodes which are running but rejecting connections.
+ differentiate between unreachable nodes and nodes which are running but rejecting connections.
- This makes it possible to see whether a node is unreachable at network level,
- or if it is running but rejecting connections for some reason.
+ This makes it possible to see whether a node is unreachable at network level,
+ or if it is running but rejecting connections for some reason.
@@ -436,7 +436,7 @@ REPMGRD_OPTS="--daemonize=false"
&repmgrd; will no longer consider nodes where &repmgrd;
- is not running as promotion candidates.
+ is not running as promotion candidates.
Previously, if &repmgrd; was not running on a node, but
@@ -474,15 +474,15 @@ REPMGRD_OPTS="--daemonize=false"
- In a failover situation, &repmgrd; will not attempt to promote a
- node if another primary has already appeared (e.g. by being promoted manually).
- GitHub #420.
-
+ In a failover situation, &repmgrd; will not attempt to promote a
+ node if another primary has already appeared (e.g. by being promoted manually).
+ GitHub #420.
+
-
-
-
+
+
+ Bug fixes
@@ -492,23 +492,23 @@ REPMGRD_OPTS="--daemonize=false"
repmgr cluster show:
- fix display of node IDs with multiple digits.
+ fix display of node IDs with multiple digits.
-
+
ensure repmgr primary unregister
- behaves correctly when executed on a witness server. GitHub #548.
+ behaves correctly when executed on a witness server. GitHub #548.
-
+
ensure repmgr standby register
- fails when is the same as the local node ID.
+ fails when is the same as the local node ID.
-
+
@@ -529,7 +529,7 @@ REPMGRD_OPTS="--daemonize=false"
&repmgr;: when executing repmgr standby switchover,
- verify the standby (promotion candidate) is currently attached to the primary (demotion candidate). GitHub #519.
+ verify the standby (promotion candidate) is currently attached to the primary (demotion candidate). GitHub #519.
@@ -537,7 +537,7 @@ REPMGRD_OPTS="--daemonize=false"
&repmgr;: when executing repmgr standby switchover,
avoid a potential race condition when comparing received WAL on the standby to the primary's shutdown location,
- as the standby's walreceiver may not have yet flushed all received WAL to disk. GitHub #518.
+ as the standby's walreceiver may not have yet flushed all received WAL to disk. GitHub #518.
@@ -551,11 +551,11 @@ REPMGRD_OPTS="--daemonize=false"
repmgr node check
- will only consider physical replication slots, as the purpose
- of slot checks is to warn about potential issues with
- streaming replication standbys which are no longer attached.
-
-
+ will only consider physical replication slots, as the purpose
+ of slot checks is to warn about potential issues with
+ streaming replication standbys which are no longer attached.
+
+
@@ -586,19 +586,19 @@ REPMGRD_OPTS="--daemonize=false"
Upgrading a major version release.
-
-
- On Debian-based systems, including Ubuntu, if using &repmgrd;
- please ensure that the in the file /etc/init.d/repmgrd, the parameter
- REPMGRD_OPTS contains "--daemonize=false", e.g.:
-
+
+
+ On Debian-based systems, including Ubuntu, if using &repmgrd;
+ please ensure that the in the file /etc/init.d/repmgrd, the parameter
+ REPMGRD_OPTS contains "--daemonize=false", e.g.:
+
# additional options
REPMGRD_OPTS="--daemonize=false"
-
-
- For further details, see repmgrd daemon configuration on Debian/Ubuntu.
-
-
+
+
+ For further details, see repmgrd daemon configuration on Debian/Ubuntu.
+
+ Configuration file changes
@@ -730,11 +730,11 @@ REPMGRD_OPTS="--daemonize=false"
repmgr 4.1.1 contains a number of usability enhancements and bug fixes.
- We recommend upgrading to this version as soon as possible.
- This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.1.0;
+ We recommend upgrading to this version as soon as possible.
+ This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.1.0;
&repmgrd; (if running) should be restarted.
See for more details.
-
+
repmgr enhancements
@@ -996,18 +996,18 @@ REPMGRD_OPTS="--daemonize=false"
repmgr witness unregister
- can be run on any node, by providing the ID of the witness node with .
- (GitHub #472).
-
-
+ can be run on any node, by providing the ID of the witness node with .
+ (GitHub #472).
+
+ repmgr standby switchover
will refuse to run if an exclusive backup is taking place on the current primary.
- (GitHub #476).
-
-
+ (GitHub #476).
+
+
@@ -1028,9 +1028,9 @@ REPMGRD_OPTS="--daemonize=false"
&repmgrd;: daemonize process by default.
- In case, for whatever reason, the user does not wish to daemonize the
- process, provide .
- (GitHub #458).
+ In case, for whatever reason, the user does not wish to daemonize the
+ process, provide .
+ (GitHub #458).
@@ -1055,23 +1055,23 @@ REPMGRD_OPTS="--daemonize=false"
repmgr cluster cleanup:
- add missing help options. (GitHub #461/#462).
-
-
+ add missing help options. (GitHub #461/#462).
+
+
- Ensure witness node follows new primary after switchover. (GitHub #453).
-
-
+ Ensure witness node follows new primary after switchover. (GitHub #453).
+
+
repmgr node check and
repmgr node status:
- fix witness node handling. (GitHub #451).
-
-
+ fix witness node handling. (GitHub #451).
+
+
@@ -1091,14 +1091,14 @@ REPMGRD_OPTS="--daemonize=false"
Release 4.0.6Thu June 14, 2018
- &repmgr; 4.0.6 contains a number of bug fixes and usability enhancements.
+ &repmgr; 4.0.6 contains a number of bug fixes and usability enhancements.
-
- We recommend upgrading to this version as soon as possible.
- This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.0.5;
+
+ We recommend upgrading to this version as soon as possible.
+ This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.0.5;
&repmgrd; (if running) should be restarted. See
for more details.
-
+ Usability enhancements
@@ -1116,33 +1116,33 @@ REPMGRD_OPTS="--daemonize=false"
repmgr standby clone:
- Improve handling of external configuration file copying, including consideration in
- check
- (GitHub #443)
+ Improve handling of external configuration file copying, including consideration in
+ check
+ (GitHub #443)
When using , force log level to INFO
- to ensure output will always be displayed
- (GitHub #441)
+ to ensure output will always be displayed
+ (GitHub #441)
repmgr standby clone:
- Improve documentation of mode
- (GitHub #438)
+ Improve documentation of mode
+ (GitHub #438)
repmgr standby clone:
- Don't require presence of user parameter in conninfo string
- (GitHub #437)
+ Don't require presence of user parameter in conninfo string
+ (GitHub #437)
@@ -1168,23 +1168,23 @@ REPMGRD_OPTS="--daemonize=false"
repmgr standby follow:
- check node has actually connected to new primary before reporting success
- (GitHub #444)
+ check node has actually connected to new primary before reporting success
+ (GitHub #444)
repmgr node rejoin:
- Fix bug when parsing parameter
- (GitHub #442)
+ Fix bug when parsing parameter
+ (GitHub #442)
&repmgrd;: ensure local node is counted as quorum member
- (GitHub #439)
+ (GitHub #439)