Dimitri Fontaine examines ten years of Postgres logical replication evolution from version 10 through 19, demonstrating how the feature has eliminated the need for external tools like Londiste and PgQ. The article begins a series exploring architectural patterns—hub-and-worker systems, consolidation, and zero-downtime upgrades—that are now possible with core Postgres functionality, using a metering system example to illustrate row filtering and column-level replication introduced in Postgres 15.
This article explores ten years of Postgres logical replication evolution since its introduction in Postgres 10. The author describes building a hub-and-workers architecture for distributed write loads using logical replication instead of older tools like Londiste, and outlines a series covering three key architectures and how successive Postgres releases have simplified the required SQL.
Lakebase Postgres uses object storage and PostgreSQL's write-ahead log (WAL) to enable agents to efficiently interact with databases by treating transaction history as the source of truth rather than current state snapshots. This transaction-centric model makes database operations like copies, restores, and replicas cheap and scalable by storing the complete timeline in object storage while data files become cached derivatives.