|repmgr 4.2 Documentation|
|Prev||Up||Appendix A. Release notes||Next|
Fri Mar 9, 2018
repmgr 4.0.4 contains some bug fixes and and a number of usability enhancements related to logging/diagnostics, event notifications and pre-action checks.
This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.0.3; repmgrd (if running) should be restarted. See Upgrading repmgr for more details.
Note: It is not possible to perform a switchover where the demotion candidate is running repmgr 4.0.2 or lower; all nodes should be upgraded to the latest version (4.0.4). This is due to additional checks introduced in 4.0.3 which require the presence of 4.0.3 or later versions on all nodes.
add repmgr standby clone --recovery-conf-only option to enable integration of a standby cloned from another source into a repmgr cluster (GitHub #382)
remove restriction on using replication slots when cloning from a Barman server (GitHub #379)
make repmgr standby promote timeout values configurable (GitHub #387)
add missing options to main --help output (GitHub #391, #392)
ensure repmgr node rejoin honours the --dry-run option (GitHub #383)
improve replication slot warnings generated by repmgr node status (GitHub #385)
fix --superuser handling when cloning a standby (GitHub #380)
repmgrd: improve detection of status change from primary to standby
repmgrd: improve reconnection to the local node after a failover (previously a connection error due to the node starting up was being interpreted as the node being unavailable)
repmgrd: when running on a witness server, correctly connect to new primary after a failover
repmgrd: add event notification repmgrd_shutdown (GitHub #393)