2026-05-05 PostgreSQL News Digest

Commits

The day brought several correctness, stability, and documentation updates, with notable fixes around REPACK, postgres_fdw, and collation-aware uniqueness reasoning.

⭐ Skip other sessions' temp tables in REPACK, CLUSTER, and VACUUM FULL

Álvaro Herrera

REPACK, CLUSTER, and VACUUM FULL had been including temporary tables from other sessions and attempting to acquire AccessExclusiveLock on them. This fix avoids a situation that could lead to long blocking.

Add missing guard for __builtin_constant_p

John Naylor — Discussion: CANWCAZbOha-x5MCreQn3TRA56VdKWNMAKMy3fAV1kJSw9Vp4pw@mail.gmail.com

This fixes an oversight in commit e2809e3a1 by adding a guard for __builtin_constant_p. On the master branch, the code was changed to use pg_integer_constant_p.

⭐ postgres_fdw: Fix handling of abort-cleanup-failed connections.

Etsuro Fujita

This fixes handling for connections whose abort cleanup failed. Previously, a connection could be dropped while open cursors remained, potentially causing a server crash.

doc: Clean up title case use

Peter Eisentraut

Title case usage in the documentation was cleaned up for consistency.

Peter Eisentraut

This commit improves message style for OAuth-related text.

⭐ Don't lose column values on REPACK

Álvaro Herrera

This fixes a REPACK issue where values could be lost for columns with defined missing values. Data integrity is preserved by forcing a rewrite when a tuple is shorter than the tuple descriptor.

Make spelling consistent

Peter Eisentraut — Discussion: CAJTYsWXFy1j_T82%2BM_S9kFxU414tQYnZQD-b82%3DoL_LbG_5fPQ%40mail.gmail.com

The spelling was made consistent by changing "vertexes" to "vertices."

doc: Small synopsis wording change for consistency

Peter Eisentraut

This slightly adjusts synopsis wording to improve consistency across the documentation.

⭐ Consider collation when proving subquery uniqueness

Richard Guo

This fixes uniqueness proofs for subqueries so they consider collation. Previously, comparisons across different collations could be treated incorrectly, so this improves query result correctness.

⭐ Consider collation when proving uniqueness from unique indexes

Richard Guo

This fixes uniqueness proofs derived from unique indexes so they consider collation. The issue dates back to the introduction of nondeterministic collations and could lead to incorrect query results.

HN News

⭐ PGKeeper: Building the bouncer we needed for Postgres

Score: 12 / Comments: 0

This article covers PGKeeper, Figma's connection pooler and bouncer for PostgreSQL. It explains Figma's approach to improving stability and security.

Postgres - Asynchronous Commits

Score: 1 / Comments: 0

This is a link to the official PostgreSQL documentation for asynchronous commits. It explains how asynchronous commit works and how it affects performance.

Summary

Today's PostgreSQL digest highlights several commits that improve database stability and data integrity, including temp-table handling in REPACK and VACUUM FULL, postgres_fdw connection error handling, and prevention of column-value loss during REPACK. The collation fixes for subquery and unique-index uniqueness proofs are especially important for result correctness. On Hacker News, Figma's new PostgreSQL bouncer PGKeeper drew attention as an example of tooling evolution in the PostgreSQL ecosystem.

This digest was generated by gemini based on Hacker News, GitHub, and the PostgreSQL mailing list.