#PostgreSQL 19 Beta review uncovered a large number of unresolved, critical design and implementation flaws in the newly developed #SQL/PGQ property graph feature, ranging from broken dependency handling, insufficient locking mechanisms, incorrect permission checks to various crashes and unexpected runtime errors, that surfaced after a broad manual and AI-assisted code review.
Given the severity and volume of these unaddressed issues, combined with the upcoming release timeline for #PostgreSQL19, the #PostgreSQL Release Management Team reached a consensus with core contributors that the feature was nowhere near production-ready.
As a result, the community ultimately decided to fully revert the entire #PGQ implementation from both the #PostgreSQL 19 stable branch and the main development master branch, to eliminate time pressure and allow developers to rework the feature properly from scratch without being constrained by backwards compatibility requirements.
Learn more: https://www.postgresql.org/message-id/flat/dqa5mstx5mna3i7s23pdwl4m6bek7gqsgfccef44wjpswizufi%403aa6vzri3cat
Given the severity and volume of these unaddressed issues, combined with the upcoming release timeline for #PostgreSQL19, the #PostgreSQL Release Management Team reached a consensus with core contributors that the feature was nowhere near production-ready.
As a result, the community ultimately decided to fully revert the entire #PGQ implementation from both the #PostgreSQL 19 stable branch and the main development master branch, to eliminate time pressure and allow developers to rework the feature properly from scratch without being constrained by backwards compatibility requirements.
Learn more: https://www.postgresql.org/message-id/flat/dqa5mstx5mna3i7s23pdwl4m6bek7gqsgfccef44wjpswizufi%403aa6vzri3cat
www.postgresql.org
PGQ catalog representation and pg_dump support
0 Replies
0 Reposts