This is part 2 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, 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 3 covers a zero-downtime major upgrade.
Database
Dimitri Fontaine: Consolidating databases with Postgres logical replication
Planet PostgreSQL0 views
Source:https://postgr.es/p/9x3
PreviousChristophe Pettus: The Deep EndNextChristophe Pettus: All Your GUCs in a Row: notify_buffers
Related posts
Every deploy gave a full share of traffic to JVMs that had not compiled anything yet
0dev.to
My Journey so Far as a Freshman Software Engineering Student at YIBS (ISEST)
0dev.to Beginners
Building Secure Authentication: Important Practices for Backend Developers
0dev.to Node
The Specification Pattern in Spring Data JPA: Building Composable Queries That Scale
0dev.to Java
How We Parsed SQLite 3 B-Tree Pages, Overflow Chains, and DuckDB SUMMARIZE in Pure TypeScript
0dev.to Database
Why Random UUID v4 Primary Keys Hurt Postgres Write Latency (And How RFC 9562 UUID v7 Fixes It)
0dev.to Database