Myths and realities of multi-master architecture in PostgreSQL
summary
Examines multi-master architecture in PostgreSQL by addressing common myths (that it is slow, hard to integrate with applications, and difficult to maintain) and presenting practical realities. Discusses concrete aspects of implementing multi-master replication in PostgreSQL, performance characteristics, integration challenges, and operational considerations based on experience and examples.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:11What is multi-master
- 3:39Replication in PostgreSQL
- 5:29Logical replication and BDR
- 6:34Multi-master requirements
- 10:14Commercial implementations
- 14:55Deploying multi-master
- 16:19Deployment tools
- 17:23Load balancers needed
- 19:56App connection
- 20:18Consistency and conflicts
- 21:45Conflict-free data types
- 24:16How conflicts work
- 26:23Resolving conflicts
- 28:09Data issues
- 30:42Cluster data comparison
- 34:11Node recovery
- 35:56Multi-master performance
- 36:49Client testing
- 38:33Performance pitfalls
- 41:48Global commit optimization
- 42:54Time synchronization
- 43:38Security and migrations
- 44:24Test results
- 45:09Where to use multi-master
- 45:31Learning resources
- 46:15Q&A
related talks
50mReplication based Multi-Master solutions and design patterns
13mBuilding reliable infrastructure with Postgres
48mChoosing a Replication System for PostgreSQL
50mMoving from MSSQL to pgSQL – High Availability and Disaster Recovery
48mPostgreSQL Replication: 20 Pitfalls and Solutions
51mPostgreSQL Replication Conflicts: Avoiding Pitfalls
14mBuilding a better PostgreSQL together
50mSparta’s Dual Kingship and PostgreSQL Active-Active