PostgreSQL: Subscription Error Handling Overhaul
Jeff Davis landed a five-commit series reworking how subscription connection info is validated and errored on, fixing restore-breaking checks, alongside separate fixes for input parsing edge cases and a tuple-deforming bug, all backpatched through version 19.
Duration: PT2M41S
Episode overview
This episode is a short developer briefing from PostgreSQL.
It explains recent repository work in plain language.
- Show: PostgreSQL
- Published: 2026-08-06T13:04:37Z
- Audio duration: PT2M41S
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 August 6th, 2026, and this is your PostgreSQL briefing.
Today's dominant story is a coordinated cleanup of subscription connection handling, driven by a security and correctness report from Noah Misch. The core problem: PostgreSQL was raising errors too eagerly when building or validating connection info for subscriptions, and that broke restores, which issue…
Jeff Davis addressed this across five commits. In 254beb1, CREATE SUBSCRIPTION stopped constructing connection info unless it's actually needed, while still checking server usage privileges. Commit 6d04cd2 went further, removing the stored connection info field entirely and generating it on demand in the caller,…
Net effect: restoring databases with subscriptions should be more reliable, and errors now surface at connection time rather than at DDL time, which is a real behavior change worth remembering if you script around subscription creation or ownership changes.
Two smaller but concrete fixes: Michael Paquier tightened parsing in tid input and in pgoutput's protocol version parameter, both using strtoul, to reject empty fields instead of behaving inconsistently across platforms — Linux and macOS…
What's…
Nearby episodes from PostgreSQL
- Hardening Recovery Paths and Wraparound Wording
- Closing Gaps Between Rules and Reality
- Correctness Fixes Across the Stack
- Weekly Recap - Correctness Fixes Across the Query Pipeline
- Clearing Up Checksums Confusion
- Quiet Bug Fixes, Loud Consequences
- Correctness Fixes Across Replication and the Planner
- Replication Fixes and a TLS Cleanup Sweep