Table of Contents Previous Next


1 Introduction : 1.1 What’s New

The following changes have been made to EDB Postgres Failover Manager 2.0 to create EDB Postgres Failover Manager 2.1:
Failover Manager now simplifies cluster startup with the auto.allow.hosts property. For more information, see Section 3.2.1.1.
Failover Manager now includes the minimum.standbys parameter, allowing you to specify how many standbys must remain in the replication scenario in the event of failover. For more information, see Section 3.2.1.1.
Failover Manager includes the auto.resume.period property; the property instructs Failover Manager to recheck the health of a failed database. For more information, see Section 3.2.1.1.
Failover Manager now supports use of an environment variable (EFMPASS) when encrypting a password. For more information, see Section 3.2.1.2.
efm promote now includes a -switchover option; the -switchover option instructs Failover Manager to perform a failover, promoting a Standby to Master, and then, return the Master node to the cluster as a Standby node. For more information, see Section 5.3.
The efm add-node command has been deprecated; while the syntax is still supported, the command is now replaced by efm allow-node. For more information, see Section 5.3.
The efm remove-node command has been deprecated; while the syntax is still supported, the command is now replaced by efm disallow-node. For more information, see Section 5.3.
The efm set-priority command allows you to set a failover priority for a Standby node. For more information, see Section 5.3.

1 Introduction : 1.1 What’s New

Table of Contents Previous Next