EDB Postgres Distributed (PGD)#
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 , Upgrading a CAMO-enabled cluster , or Eager All-Node Replication Replication.
- General Information
- Compatibility)
- EDB Postgres Distributed release notes
- EDB Postgres Distributed 5.5.1 release notes
- EDB Postgres Distributed 5.5.0 release notes
- EDB Postgres Distributed 5.4.1 release notes
- EDB Postgres Distributed 5.4.0 release notes
- EDB Postgres Distributed 5.3.0 release notes
- EDB Postgres Distributed 5.2.0 release notes
- EDB Postgres Distributed 5.1.0 release notes
- EDB Postgres Distributed 5.0.1 release notes
- EDB Postgres Distributed 5.0.0 release notes
- Known issues
- Concepts
- Terminology
- Asynchronous replication
- Commit scopes
- CAMO or commit-at-most-once
- Conflicts
- Consensus
- Cluster
- DDL (data definition language)
- DML (data manipulation language)
- Eager
- Eventual consistency
- Failover
- Group commit
- Immediate consistency
- Logical replication
- Node
- Node groups
- PGD cluster
- PGD node
- Physical replication
- Postgres cluster
- Quorum
- Replicated available fault tolerance (Raft)
- Read scalability
- Subscription
- Switchover
- Synchronous replication
- Subscriber-only nodes
- Two-phase commit (2PC)
- Vertical scaling or scale up
- Witness nodes
- Write leader
- Writer
- PGD overview
- Terminology
- Get Started
- Using
- Administration
- 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
- PGD Proxy
- Backup and recovery
- Security and roles
- Monitoring
- Testing and tuning PGD clusters
- Upgrading
- Node management
- Tools
- PGD Features
- PGD reference
- User visible catalogs and views
- System functions
- PGD settings
- Exploring conflict handling with PGD
- Global sequence parameters
- DDL handling
- Global locking
- Node management
- Generic replication
- State-based and operation-based CRDTs
- Commit scopes
- Commit At Most Once
- Transaction streaming
- Lag Control
- Timestamp-based snapshots
- Monitoring and logging
- Decoding worker
- Connectivity settings
- Internal settings - Raft timeouts bdr.raft_global_election_timeout
- Internal settings - Other Raft values
- Internal settings - Other values
- Node management
- Node management interfaces
- Routing functions
- Commit scopes
- Replication set management
- Replication set membership
- DDL replication filtering
- Testing and tuning commands
- Global sequence management interfaces
- PGD AutoPartition
- Stream triggers reference
- Stream triggers manipulation interfaces
- Stream triggers row functions
- Stream triggers row variables
- Internal catalogs and views
- Internal system functions
- PGD Compatibility by PostgreSQL Version