PostgreSQL: Infrastructure Transition and Graph Table Fixes
PostgreSQL completed a major infrastructure transition from Cirrus CI to GitHub Actions following Cirrus's shutdown, while addressing critical bugs in the new graph table feature and fixing several Unicode and permission issues.
Duration: PT2M1S
Transcript
Good morning. This is your PostgreSQL development briefing for June 5th, 2026.
The biggest change this week was PostgreSQL's complete transition from Cirrus CI to GitHub Actions, prompted by Cirrus CI shutting down on June 1st. This infrastructure shift, implemented in commits 9c12606 and 68c8a36, maintains comprehensive testing across Linux, macOS, and Windows platforms while requiring repositories to explicitly opt into CI by setting a repository variable. This ensures continuity for the project's quality assurance without disrupting existing development workflows.
Two significant fixes landed for the graph table feature, which appears to be receiving active stabilization. Commit 4cb2a98 resolved crashes in multi-label pattern queries by fixing how lateral references are handled when graph tables are rewritten as union subqueries. A separate fix in commit 72498a8 addressed event trigger compatibility by properly handling property graph objects in the object address system, ensuring these objects work correctly with database event mechanisms.
Several permission and encoding issues were also resolved. The subscription system gained proper column-level privileges for the wal receiver timeout setting, while the text search functions received improved error handling to prevent invalid encoding issues when reporting weight symbol errors. A Unicode normalization bug affecting Hangul characters was fixed, specifically addressing incorrect handling of the TBASE syllable.
Looking ahead, developers should verify their CI configurations are properly enabled if working with PostgreSQL forks, and expect continued stabilization work on graph table functionality as these features mature. The infrastructure changes should be transparent for most contributors, but may require attention for custom CI setups.
That's your PostgreSQL briefing. Stay informed, stay building.