PostgreSQL: Closing the Gaps Between Related Commands

Today's commits center on fixing mismatches where one code path enforced a rule that a related, similar path forgot — in permissions, security, view checks, and command options. Nathan Bossart, Tom Lane, Peter Eisentraut, and Michael Paquier each closed one of these gaps.

Duration: PT2M28S

Episode overview

This episode is a short developer briefing from PostgreSQL.

It explains recent repository work in plain language.

  • Show: PostgreSQL
  • Published: 2026-08-14T13:03:45Z
  • Audio duration: PT2M28S

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 14th, 2026, and this is your PostgreSQL briefing.

The throughline today: several fixes address cases where Postgres enforced a rule in one place but forgot it in a related one. That pattern shows up across permissions, security, and command handling.

Start with roles. Nathan Bossart's fix, commit a8261c7, addresses an authorization check for role membership that used one method to decide if a grant was allowed, and a different method to find the grantor. When the two disagreed, users got a confusing internal error instead of a clean permission denial. The fix,…

Same pattern in view security. Peter Eisentraut's commit 9924e2d fixes DELETE FOR PORTION OF, used with temporal tables, which inserts leftover rows but wasn't getting the WITH CHECK OPTION treatment that regular inserts and updates get. That meant rows could quietly bypass a view's check constraint. Now it's…

And in command options, Nathan Bossart's commit ac5cea8 rejects CLUSTER with ANALYZE, an unintended side effect of the newer REPACK command. It technically worked on single tables but broke on partitioned or database-wide runs. Rather than fix it further, it's simply disallowed, keeping CLUSTER…

S…

Nearby episodes from PostgreSQL

  1. Small Fixes, Steady Hardening
  2. Weekly Recap - Cleanup, Correctness, and Closing Old Doors
  3. Housekeeping and Code Clarity
  4. Cleanup, Correctness, and Retiring Old Interfaces
  5. Correctness Fixes Across Replication, Stats, and Tooling
  6. Tightening Up Input Handling and Storage Defaults
  7. A Security Patch Batch Lands
  8. Correctness and Crypto Cleanup