Postgres as a Service
Deploy a Managed Postgres Cluster in Minutes! Enterprise-ready and Oracle compatible.
Creating a Failover Manager cluster is a relatively simple process. After creating a Postgres streaming replication scenario and ensuring that the nodes have sufficient permissions to communicate with each other, you must:Failover Manager is packaged and delivered as an RPM. To install Failover Manager, copy the RPM package to the Master, Standby and Witness systems. After copying the archive to each system, use yum to install the package:# yum install efm20-x.x.x-x.distribution.rpmFailover Manager must be installed by root. During the installation process, the installer will also create a user named efm that has sufficient privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see Section 3.1, Extending Failover Manager Permissions.
2. Modify the cluster properties file on each node. For detailed information about modifying the cluster properties file, see .
• Executables: /usr/efm-2.0/bin
• Libraries: /usr/efm-2.0/lib
• Cluster configuration files: /etc/efm-2.0
• Logs: /var/log/efm-2.0
• Lock files: /var/lock/efm-2.0
• Log rotation file: /etc/logrotate.d/efm-2.0
• sudo configuration file: /etc/sudoers.d/efm-20