PostgreSQL: Weekly Recap - Data Integrity & Infrastructure Hardening
This week's 30 commits focused heavily on data checksums reliability and infrastructure compatibility, with significant fixes for standby promotion scenarios and encoding handling in the new JSON copy format.
Duration: PT2M39S
Transcript
Welcome to PostgreSQL Weekly Recap for May 25th through June 1st, 2026.
Zero pull requests merged, 30 additional commits this week.
The dominant theme was data integrity hardening, particularly around PostgreSQL's checksum functionality during complex deployment scenarios.
**Data Checksums Reliability**
Multiple commits from Daniel Gustafsson addressed critical issues in checksum state management. The most significant fix, commit 5fee7ca, resolved a serious bug during standby promotion where processes could end up with inconsistent checksum states. When a standby gets promoted to primary during checksum enabling, it now properly emits process signal barriers to ensure all processes see the correct state transition. Additional commits standardized naming conventions and improved documentation around checksum processes, moving from "datachecksum" to the plural "datachecksums" for consistency.
**Format and Encoding Fixes**
The new JSON format for COPY TO received an important encoding fix in commit 7dc5bbc. Previously, JSON output bypassed encoding conversion entirely, meaning operations specifying Latin-1 encoding would silently produce UTF-8 output instead. The fix ensures JSON follows the same encoding conversion path as text and CSV formats, applying server-to-client conversion to the complete JSON buffer.
**Infrastructure Compatibility**
Forward compatibility got attention with commit 89d243d preparing PostgreSQL for OpenSSL 4.0. The changes handle parameter and return value modifications in the upcoming OpenSSL release, updating declarations and adding necessary type casting. This work will be backpatched to all supported branches since any version could encounter OpenSSL 4.0 as it reaches distributions.
**Developer Experience Improvements**
Several smaller but notable fixes improved the developer experience. The pg_plan_advice feature received a syntax fix for the DO_NOT_SCAN tag, and the pg_available_extensions view now properly reports symbolic system paths instead of leaking actual filesystem locations. REPACK CONCURRENTLY operations also gained better WAL management, allowing old WAL recycling during long-running repack operations.
Next week, watch for the OpenSSL 4.0 compatibility changes to appear in backpatched form across supported branches, and continued refinement of the checksum functionality as these fixes get broader testing.
That's your PostgreSQL weekly recap.