PostgreSQL: GSS Leak Fix and Concurrency Crash Fixes

Repeated GSS connections leaked credentials memory due to redundant acquisition, now fixed and back-patched to version 16. The broader pattern is small correctness hardening across error reporting, concurrent schema handling, and test stability.

Duration: PT2M34S

Episode overview

This episode is a short developer briefing from PostgreSQL.

It explains recent repository work in plain language.

  • Show: PostgreSQL
  • Published: 2026-10-31T13:03:15Z
  • Audio duration: PT2M34S

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 October 31st, 2026, and this is your PostgreSQL developer briefing.

The lead signal today is reliability hardening in edge cases, topped by a client-side memory leak in GSS authentication that could accumulate significantly with repeated connections.

First theme is connection and concurrency safety. In commit 1c9efb5, the credential check acquired new GSS credentials on every pass through the connection loop, leaking the previous handle — about 16 kilobytes per cycle according to the reporter. The fix renames that helper to clarify it always allocates, removes…

Second, sharper error semantics. Commit 46d7c16 fixes PL/pgSQL end-of-input handling, where an unused terminator slot matched end of file and produced generic syntax errors instead of specific missing-token messages like missing THEN. Commit 426551c makes the string-to-integer helper return maximum or minimum…

Finally, data and test maintenance. Time zone data moves to release 2026f in commit cb3a90c, with Cuba staying on daylight time this winter and historical corrections for Brazil. Two test fixes improve stability: cluster setup no longer applies the current initialization template to older versions,…

What…

Nearby episodes from PostgreSQL

  1. Wrong-Result Fixes and Memory Hardening
  2. Backup Safety, Planner Correctness, and Maintenance Tuning
  3. Stale Cache Fixes and Backup Data Loss
  4. Weekly Recap - Executor Correctness and Data Safety
  5. Planner Correctness and Crash Fixes
  6. Planner Correctness and JSON Error Handling
  7. TOAST, Backup and Hash Table Reliability Fixes
  8. Query Tracking Overhaul and Data Integrity Fixes