PostgreSQL: Hardening Edge Cases in Replication and Test Stability

Today's commits center on fixing subtle correctness bugs in logical replication conflict detection and backend shutdown, alongside a cluster of test-stability fixes for flaky buildfarm failures.

Duration: PT2M48S

Episode overview

This episode is a short developer briefing from PostgreSQL.

It explains recent repository work in plain language.

  • Show: PostgreSQL
  • Published: 2026-09-03T13:04:21Z
  • Audio duration: PT2M48S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good day, and welcome to the PostgreSQL briefing for September 3rd, 2026.

The core story today is correctness under edge cases—places where timing, concurrency, or rare configurations could cause silent problems or indefinite hangs.

Start with logical replication. Amit Kapila's commit, 5f3a49a, fixes a real risk in the retain dead tuples feature: when a publisher uses asynchronous commit, the reported WAL position could lag behind an actually-committed transaction. That meant dead tuples needed for conflict detection could be removed too early.…

Related in spirit is Fujii Masao's fix in commit 0b776de, addressing a backend hang. Sessions with deferrable serializable read-only transactions could get stuck indefinitely during temp table cleanup at exit, even immune to pg_terminate_backend, if a conflicting transaction was prepared. The fix switches cleanup to…

Also worth noting: Michael Paquier reverted a prior change to statistics import functions in commit 6fe9b62, citing unresolved design discussion around the interface for foreign data wrapper code. A reminder that not every merged change is final—sometimes the right move is stepping back.

The second theme is test stability. Three…

Nearby episodes from PostgreSQL

  1. Query Planner Correctness Fixes and Version 19 Cleanup
  2. Integer Overflow Cleanup Across the Tree
  3. Closing the Coverage Gap on Custom Scans
  4. Weekly Recap - Correctness Fixes and Shared Memory Hardening
  5. Dictionary Parsing Gets Hardened
  6. Correctness Fixes for Query Planning and Shared Memory
  7. Widening Fixes and Planner Corrections Land as Backpatches
  8. Retreat and Repair