PostgreSQL Replication Conflicts: Avoiding Pitfalls
summary
Covers common replication conflicts in PostgreSQL streaming replication—such as replication lag, logical slots, lock and snapshot conflicts, and tablespace issues—and explains PostgreSQL internals behind those problems. Describes best practices and observability tools (monitoring/diagnostics) to prevent and troubleshoot replication-related failures.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:23Replication Issues - Overview • Reliable replication scheme requires: Optimal configuration
- 4:47Presentation Outline
- 17:10Synching Up • Synchronous Streaming Replication
- 21:53Replication Configuration • Configuration Parameters Sending Server
- 25:55What Conflicts? So primary server and readonly standby. How can we have conflicts?
- 27:04Replication Issues?
- 27:41Types of Replication Issues Faced
- 32:34Replication: Lock Conflict
- 34:09Lock Conflict-Code Flow
- 44:07Replication: Snapshot Conflicts Primary Server Standby Server
- 44:34Snapshot Conflicts-Code Flow Start XLog Processing
- 45:56Closing Thoughts Always tune for workload. There is no single solution that fits
related talks
42mPostgreSQL Replication Conflicts: Avoiding Pitfalls
48mPostgreSQL Replication: 20 Pitfalls and Solutions
51mPostgreSQL Replication Conflicts: Avoiding Pitfalls
49mDebugging and Troubleshooting PostgreSQL Streaming Replication
49mPostgreSQL Replication - The Most Exciting Technology on Earth
22mSecuring Postgres with streaming replication
02h 26mTutorial
52mNew Data Replication Technologies in PostgreSQL
