Thu Feb 15, 2018
repmgr 4.0.3 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.2; repmgrd (if running) should be restarted.
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 4.0.3. 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.
improve repmgr standby switchover behaviour when pg_ctl is used to control the server and logging output is not explicitly redirected
improve repmgr standby switchover log messages and provide new exit code ERR_SWITCHOVER_INCOMPLETE when old primary could not be shut down cleanly
add check to verify the demotion candidate can make a replication connection to the promotion candidate before executing a switchover (GitHub #370)
add check for sufficient walsenders and replication slots on the promotion candidate before executing repmgr standby switchover (GitHub #371)
add --dry-run mode to repmgr standby follow (GitHub #368)
add standby_register_sync event notification, which is fired when repmgr standby register is run with the --wait-sync option and the new or updated standby node record has synchronised to the standby (GitHub #374)
when running repmgr cluster show, if any node is unreachable, output the error message encountered in the list of warnings (GitHub #369)
ensure an inactive data directory can be overwritten when cloning a standby (GitHub #366)
repmgr node status upstream node display fixed (GitHub #363)
repmgr primary unregister: clarify usage and fix --help output (GitHub #373)
parsing of pg_basebackup_options fixed (GitHub #376)
ensure the pg_subtrans directory is created when cloning a standby in Barman mode
repmgr witness register: fix primary node check (GitHub #377).