Replication Refresh
summary
PostgreSQL 9.3 adds concrete replication behavior: physical WAL streaming with hot standby read-only queries, per-transaction durability levels (including maximum durability), and fast failover that skips a checkpoint to promote a standby in under a second. Synchronous replication guarantees a commit is safe on at least one other node so you can achieve zero data loss if you configure multiple standbys; asynchronous streaming yields low latency (commit propagation often ~50 ms) but vacuum or bursts spike lag. Logical replication work and timeline following expand options.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:19Refresher
- 1:09Topics
- 1:52Basic Replication Concepts
- 3:26libpq connection
- 4:04Connect to Source
- 5:42Plugin
- 6:43Additional Security
- 8:02Multiple Receivers
- 10:24Efficient and Concurrent
- 12:35Cascading Replication
- 14:20Access to Receiver nodes
- 16:00Visibility of changes
- 22:32Latency
- 28:32Synchronous Replication
- 30:33Synchronous Guarantee
- 35:11Synchronous Visibility
- 37:17synchronous_commit
- 39:44Fluid Dynamics
- 41:46Physical Replication
- 42:14PostgreSQL 9.2 Replication
related talks
22mSecuring Postgres with streaming replication
49mPostgreSQL Replication - The Most Exciting Technology on Earth
53mThe journey towards active replication in PostgreSQL
26mMyths and Truths about Synchronous Replication in PostgreSQL
42mPostgreSQL Replication Conflicts: Avoiding Pitfalls
24mPostgreSQL physical replication - internals, latest development and opportunities
44mThe journey towards active-active replication in PostgreSQL
48mPostgreSQL Replication: 20 Pitfalls and Solutions