Dimitri Fontaine: Zero-downtime Postgres upgrades with logical replication
This is part 3 of a series about Postgres logical replication use-cases, and about how the feature set has evolved over the past ten years and ten releases (Postgres 10 through the Postgres 19 beta), one architecture at a time.
Executive Summary
This is part 3 of a series about Postgres logical replication use-cases, and about how the feature set has evolved over the past ten years and ten releases (Postgres 10 through the Postgres 19 beta), one architecture at a time. Part 1 built a hub-and-workers system for write scalability and has the table of what each release added, which this post assumes. Part 2 consolidated several application databases into one warehouse.
Database Engine & Storage Subsystem Architecture
From an OLTP/OLAP systems architecture, storage tiering, and data durability perspective: - **Zero-Vendor Lock-in Formats:** Leveraging open specifications (e.g. Parquet, Iceberg) ensures multi-engine interoperability without ingestion lock-in. - **Vector & In-Memory Throughput:** Modern memory layouts and SIMD-accelerated execution pipelines minimize latency in real-time retrieval. - **Distributed Resiliency:** Decoupled storage and compute layers enable elastic horizontal scaling with strict ACID guarantees.
Impact on the Open Ecosystem
Empowers data engineers with open, self-hosted alternatives to monopolistic cloud database providers.