Welcome to pg_auto_failover’s documentation!
- Introduction to pg_auto_failover
- Main pg_autoctl commands
- pg_auto_failover Tutorial
- Architecture Basics
- Multi-node Architectures
- Failover State Machine
- Failover and Fault Tolerance
- Installing pg_auto_failover
- Security settings for pg_auto_failover
- Manual Pages
- pg_autoctl
- pg_autoctl create
- pg_autoctl drop
- pg_autoctl config
- pg_autoctl show
- pg_autoctl enable
- pg_autoctl disable
- pg_autoctl get
- pg_autoctl set
- pg_autoctl perform
- pg_autoctl do
- pg_autoctl run
- pg_autoctl watch
- pg_autoctl stop
- pg_autoctl reload
- pg_autoctl status
- Configuring pg_auto_failover
- Operating pg_auto_failover
- Deployment
- Provisioning
- Upgrading pg_auto_failover, from versions 1.4 onward
- Upgrading from previous pg_auto_failover versions
- Extension dependencies when upgrading the monitor
- Cluster Management and Operations
- Current state, last events
- Monitoring pg_auto_failover in Production
- Replacing the monitor online
- Trouble-Shooting Guide
- Frequently Asked Questions
- I stopped the primary and no failover is happening for 20s to 30s, why?
- The secondary is blocked in the CATCHING_UP state, what should I do?
- Should I read the logs? Where are the logs?
- The state of the system is blocked, what should I do?
- The monitor is a SPOF in pg_auto_failover design, how should we handle that?