Using#
EDB Postgres Distributed (PGD) provides multi-master replication and data distribution with advanced conflict management, data-loss protection, and throughput up to 5X faster than native logical replication . It enables distributed Postgres clusters with high availability up to five 9s.
By default, EDB Postgres Distributed uses asynchronous replication, applying changes on the peer nodes only after the local commit. You can configure additional levels of synchronicity between different nodes, groups of nodes, or all nodes by configuring Group commit , CAMO or commit-at-most-once <CAMO or commit-at-most-once> , or Eager Replication.
- Application use
- Node management
- Node types
- Groups and subgroups
- Creating and joining PGD groups
- Witness nodes
- Logical standby nodes
- Subscriber-only nodes and groups
- Viewing PGD topology
- Removing nodes and groups
- Joining a heterogeneous cluster
- Connection DSNs and SSL (TLS)
- Decoding worker
- Replication slots created by PGD
- Node restart and down node recovery
- Maintenance commands through proxies
- Postgres configuration
- DDL replication
- Security and roles
- Sequences
- Durability
- Consistency
- Parallel Apply
- Replication sets
- Application connection management
- Backup and recovery
- Monitoring
- OpenTelemetry integration
- Monitoring through SQL
- Monitoring overview
- Monitoring node join and removal
- Monitoring Replication Peers
- Monitoring PGD replication workers
- Monitoring PGD writers
- Monitoring global locks
- Monitoring conflicts
- Apply statistics
- Standard PostgreSQL statistics views
- Monitoring PGD versions
- Monitoring Raft consensus
- Monitoring replication slots
- Monitoring transaction COMMITs
- EDB Postgres Distributed Command Line Interface
- Transaction streaming
- Testing and tuning PGD clusters
- Stream triggers
- AutoPartition
- Explicit two-phase commit (2PC)
- Timestamp-based snapshots