Tue July 31, 2018
repmgr 4.1.0 introduces some changes to repmgrd behaviour and some additional configuration parameters.
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:
Execute ALTER EXTENSION repmgr UPDATE on the primary server in the database where repmgr is installed.
repmgrd must be restarted on all nodes where it is running.
A restart of the PostgreSQL server is not required for this release (unless upgrading from repmgr 3.x).
See Upgrading repmgr 4.x and later for more details.
Configuration changes are backwards-compatible and no changes to repmgr.conf are required. However users should review the changes listed below.
Note: Repository changes
Coinciding with this release, the 2ndQuadrant repository structure has changed. See section Installing from packages for details, particularly if you are using a RPM-based system.
Default for log_level is now INFO. This produces additional informative log output, without creating excessive additional log file volume, and matches the setting assumed for examples in the documentation. (GitHub #470).
recovery_min_apply_delay now accepts a minimum value of zero (GitHub #448).
repmgr: always exit with an error if an unrecognised command line option is provided. This matches the behaviour of other PostgreSQL utilities such as psql. (GitHub #464).
repmgr: add -q/--quiet option to suppress non-error output. (GitHub #468).
Add --csv output option for repmgr cluster event. (GitHub #471).
repmgr witness unregister can be run on any node, by providing the ID of the witness node with --node-id. (GitHub #472).
repmgr standby switchover will refuse to run if an exclusive backup is taking place on the current primary. (GitHub #476).
repmgrd: create a PID file by default (GitHub #457). For details, see repmgrd's PID file.
repmgrd: daemonize process by default. In case, for whatever reason, the user does not wish to daemonize the process, provide --daemonize=false. (GitHub #458).
repmgr standby register --wait-sync: fix behaviour when no timeout provided.
repmgr cluster cleanup: add missing help options. (GitHub #461/#462).
Ensure witness node follows new primary after switchover. (GitHub #453).
When using repmgr standby clone with --recovery-conf-only and replication slots, ensure primary_slot_name is set correctly. (GitHub #474).