PostgreSQL: Stale Cache Fixes and Backup Data Loss
The day centers on silent correctness bugs — wrong query results from reused executor caches and missing blocks in incremental backups. Several fixes for Memoize, hashed subplans, backup merging, and prepared transactions are backpatched to stable branches.
Duration: PT2M22S
Episode overview
This episode is a short developer briefing from PostgreSQL.
It explains recent repository work in plain language.
- Show: PostgreSQL
- Published: 2026-11-02T14:02:51Z
- Audio duration: PT2M22S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
It's Monday, November 2nd, 2026, and this is your PostgreSQL briefing.
The throughline today is silent wrong data — the most serious class of bug — with fixes for query results, backups, and constraints.
First, executor caching. Two changes fix cases where cached results were reused after parameters changed, documented in commits 303c9b3 and 708eb51. One involves duplicated hashed subplans sharing state, where a rescan could clear the change signal before all copies rebuilt their hash tables, leaving stale data in…
Second, durability and replication. An incremental backup fix in commit d903620 addresses data loss when a relation is truncated and extended: summaries were merged out of order, which could drop modified blocks and, when combined, restore stale data with live rows missing. A separate two-phase commit fix in commit…
Finally, hardening. New compiler annotations describe flexible array sizes to catch overruns earlier, and PL Python moves pseudotype checks into validation to catch bad functions at creation time rather than on every call.
What's next: most correctness fixes are backpatched to supported releases, so expect stable-branch updates and re-test Memoize and subplan…
Nearby episodes from PostgreSQL
- Window Hangs, Planner Crashes and Replication Hardening
- Silent Correctness Fixes for Backups, Sorting and JSON
- Wrong-Result Fixes and Memory Hardening
- Backup Safety, Planner Correctness, and Maintenance Tuning
- Weekly Recap - Executor Correctness and Data Safety
- GSS Leak Fix and Concurrency Crash Fixes
- Planner Correctness and Crash Fixes
- Planner Correctness and JSON Error Handling