PostgreSQL: Logical Replication Cleanup Continues
Today's commits center on tightening up logical replication correctness, from sequence synchronization bugs to a faster invalidation lookup, alongside a JSON deparsing fix and new index test coverage. The through-line: multiple contributors are hardening edge cases in replication that only surface under specific timing or catalog conditions.
Duration: PT2M19S
Episode overview
This episode is a short developer briefing from PostgreSQL.
It explains recent repository work in plain language.
- Show: PostgreSQL
- Published: 2026-07-27T13:03:08Z
- Audio duration: PT2M19S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 27th, 2026, and this is your PostgreSQL briefing.
Today's theme is logical replication correctness, with three separate commits touching how Postgres tracks and synchronizes replicated state.
The headline fix comes from Amit Kapila, addressing a batch of issues in sequence synchronization for logical replication. The core bug: a sequence sync worker could keep running after a subscription was disabled, because it wasn't rereading its subscription state after starting a transaction. The fix brings it in…
Related in spirit, Michael Paquier landed a performance fix for partition map invalidation, replacing a linear hash scan with a direct lookup. Small change, but it removes a long-standing to-do item and speeds up invalidation callbacks for workloads with many partitioned relations.
Second theme: correctness in less common SQL paths. Richard Guo fixed a deparsing bug where JSON array construction from a subquery would silently drop its format clause when reconstructing the original query text — a real semantic bug, since format JSON changes whether a value is treated as raw JSON or a quoted…
Separately, Peter Geoghegan added test coverage for B-tree start-key…
Nearby episodes from PostgreSQL
- Weekly Recap - Logical Replication Hardening & Test Coverage
- Hardening the B-tree Index Under Concurrency
- Getting Permission Checks Right
- Publication Testing and Docs Get a Cleanup
- Version 19's Growing Pains
- Polish Pass on Messages and Edge Cases
- Cleaning Up After Recent Features
- Closing the Gaps Between Correctness and Convention