repmgr 4.2 – Now with support for PostgreSQL 11
Oxford, United Kingdom – October 24, 2018
2ndQuadrant today announced the release of repmgr 4.2. This release includes support for PostgreSQL 11, the newest major release announced by the community last week.
repmgr is the most popular tool for PostgreSQL replication and failover management. It enhances and complements the built-in replication capabilities in PostgreSQL; making it easy to set up and manage standby servers, check replication status, and perform administrative tasks such as switchover operations. The repmgrd daemon provides automatic failover capability to maximize database uptime, and can easily be integrated with other tools such as PgBouncer for high application availability.
The principal new feature of repmgr 4.2 is the ability to “pause” the repmgr daemon (repmgrd) via the repmgr daemon pause and the corresponding repmgr daemon unpause commands. These will temporarily prevent it from taking failover action. This is useful for activities like planned maintenance (e.g. database upgrades or switchovers) which previously required repmgrd to be shut down on all nodes. repmgr standby switchover will automatically pause/unpause repmgrd, simplifying switchover operations.
Additionally, the new repmgr daemon status command is available to provide an overview of repmgrd status on all nodes.
For more details on this functionality, see the detailed documentation.
repmgr 4.2 also provides several usability enhancements:
- Add new parameter shutdown_check_timeout (default: 60 seconds). This provides an explicit timeout for repmgr standby switchover to check that the demotion candidate (current primary) has shut down.
- Add new parameter repmgr_bindir. This facilitates remote invocation of repmgr when the repmgr binary is located somewhere other than the PostgreSQL binary directory, as it cannot be assumed all package maintainers will install repmgr there. This parameter is optional; if not set (default), repmgr will fall back to pg_bindir (if set).
- repmgr cluster cleanup now accepts the --node-id option to delete records for only one node.
- When running repmgr cluster matrix and repmgr cluster crosscheck, repmgr will report nodes unreachable via SSH, and emit return code ERR_BAD_SSH.
For a detailed list of all changes, please read the complete release notes here.
Upgrade instructions are available here.
Packages and installation documentation are available via 2ndQuadrant’s public RPM and APT repositories from 2ndQuadrant here.
repmgr is distributed under GPL v3.
For more information, please send an email to [email protected]