Automatic DDL Replication with pgEdge Distributed Postgres
summary
Automatic DDL replication for a multimaster Postgres mesh is implemented in pgEdge: logical replication plus a Spock extension layer, Snowflake sequences, a pg_partman hook for partitions and an LOL extension for large objects. Configuration uses three GUCs (toggle with enable_ddl_replication and reload without restart), an anti‑chaos engine that makes nodes eventually consistent, and Raft consensus under the hood. Tables without PKs go to a default insert-only replication set and schema changes propagate across nodes.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:09Logical replication challenges
- 3:19PG Edge multimaster overview
- 5:12PG Edge architecture and extensions
- 7:22Need for auto DDL replication
- 9:50Community Postgres limitations
- 13:26PG Edge DDL replication features
- 17:51Production best practices
- 20:40Why use PG Edge
- 22:28Q&A and conclusion
related talks
53mMulti master replication for painless fault tolerance
50mReplication based Multi-Master solutions and design patterns
44mThe journey towards active-active replication in PostgreSQL
31mPast, Present, and Future: Logical Decoding and Replication in PostgreSQL
46mpg paxos Table Replication through Distributed Consensus
56mLogical Replication of DDLs
53mThe journey towards active replication in PostgreSQL
50mMoving from MSSQL to pgSQL – High Availability and Disaster Recovery