Failover Manager 4.5 release notes v4
Released: 30 Aug 2022
Enhancements, bug fixes, and other changes in EFM 4.5 include:
|Failover Manager has been upgraded to use PostgreSQL JDBC Driver version 42.4.1 to address security vulnerability CVE-2022-31197. Note: Failover Manager is not impacted by the vulnerability, but no longer contains the impacted version of the library.
|When a primary node has been isolated from the cluster and rejoins, if no other node has been promoted, Failover Manager will restart the isolated database and resume monitoring as the primary node in the cluster. [Support tickets #937960, #968619, #81770, #81894]
|Failover Manager will now properly choose a standby to promote in rare cases of LSN values being compared incorrectly. [Support ticket #83186]
|Failover Manager now handles extra whitespace in the properties file when running the
efm command for cluster status.
|Failover Manager will no longer fail to promote in rare cases where the primary agent is running slowly. [Support ticket #79847]
|Failover Manager properly follows the promotable=false value of a standby that is restarted after being made promotable manually through the
efm command. [Support ticket #83192]
|When using physical replication slots, Failover Manager will now drop and recreate slots on standbys when advancing the LSN values on them if they have an
xmin value set. [Support ticket #83910]
|Systemd status will now show "inactive" status instead of "failed" after being used to stop a Failover Manager agent.