EDB Postgres Distributed¶
EDB Postgres Distributed provides multi-master replication and data distribution with advanced conflict management, data-loss protection, and throughput up to 5X faster than native logical replication, and enables distributed PostgreSQL clusters with high availability up to five 9s.
node diagram¶
By default EDB Postgres Distributed uses asynchronous replication, applying changes onthe peer nodes only after the local commit. Additional levels of synchronicity canbe configured between different nodes, groups of nodes or all nodes by configuring CAMO or commit-at-most-once ,
Group Commit , or eager all node replication features.
- Release notes
- ‘Known issues’
- Key components
- Terminology
- Asynchronous replication
- Availability
- CAMO or commit-at-most-once
- Clustering
- Data sharding
- Eager Replication for BDR
- Eventual consistency
- Failover
- Horizontal scaling or scale out
- Logical replication
- Nines
- Node
- Physical replication
- Read scalability
- Recovery point objective (RPO)
- Recovery time objective (RTO)
- Single point of failure (SPOF)
- Switchover
- Synchronous replication
- Two-phase commit (2PC)
- Vertical scaling or scale up
- Write scalability
- Choosing your architecture
- Choosing a Postgres distribution
- Choosing durability
- Other considerations
- Deployment options
- Upgrading
- Compatibility matrix
- Backup and recovery
- Monitoring
- Monitoring Overview
- Monitoring Node Join and Removal
- Monitoring Replication Peers
- Monitoring BDR Replication Workers
- Monitoring BDR Writers
- Monitoring Global Locks
- Monitoring Conflicts
- External Monitoring
- Apply Statistics
- Standard PostgreSQL Statistics Views
- Monitoring BDR Versions
- Monitoring Raft Consensus
- Monitoring Replication Slots
- Monitoring Transaction COMMITs
- PGD CLI
