Maintaining your PGD cluster#
EDB Postgres Distributed (PGD) provides a suite of tools and methodologies for maintaining the health of your multi-master clusters, keeping performance tuned and your data protected through regular testing and backups.
Testing and tuning PGD clusters - Guidance on benchmarking your distributed workloads using
pgd-benchand optimizing system parameters for maximum throughput.Backup and recovery - Best practices for securing your data, including physical and logical backup strategies tailored for distributed multi-master topologies.
Monitoring the Connection Manager - Tracking cluster health through Postgres Enterprise Manager, SQL, and PGD Monitor’s built-in web UI, REST API, and Prometheus endpoint.
- Testing and tuning PGD clusters
- Backup and recovery
- Logical backup and restore
- Physical backup and restore
- Restore
- EDB Postgres Distributed cluster failure or seeding a new cluster from a backup
- Cleanup of PGD metadata
- Cleanup of replication origins
- Cleanup of replication slots
- Setting
max_worker_processeson a manual restore - Recreating logical replication slots
- Extension catalog tables that aren’t in any replication set
- Eventual consistency
- Monitoring
- Monitoring
- Monitoring through SQL
- Monitoring overview
- Monitoring node join and removal
- Monitoring the manager worker
- Monitoring Routing
- Monitoring Replication Peers
- Monitoring PGD replication workers
- Monitoring PGD writers
- Monitoring commit scopes
- Monitoring global locks
- Monitoring conflicts
- Apply statistics
- Standard PostgreSQL statistics views
- Monitoring PGD versions
- Monitoring Raft consensus
- Monitoring replication slots
- Monitoring transaction COMMITs
- Using the PGD Monitor
- Monitoring through SQL
- Migrating to Postgres Distributed (PGD)