#pgq

Chirps tagged with #pgq

Oracle AI Database 26ai adds native support for Operational Property Graphs through #SQL/#PGQ, allowing developers to query connected data directly with #SQL. The webcast demonstrates Oracle’s integration with Linkurious’ Ogma library, showing how graph queries can be turned into interactive visualizations of large-scale networks without complex data pipelines or transformations:

https://us02web.zoom.us/webinar/register/2917289133152/WN_0Czk-h_mTk6MYy8-VedxVg#/registration

Open Graph Image
us02web.zoom.us

Welcome! You are invited to join a webinar: Graph Analytics with Oracle AI Database 26ai and Linkurious Ogma. After registering, you will receive a confirmation email about joining the webinar.

Graph data is essential for understanding complex relationships in modern applications. Oracle AI Database 26ai introduces native support for Operational Property Graphs via SQL/PGQ, enabling developers to model and query connected data directly with SQL. In this technical webcast, Oracle and Linkurious showcase a new integration with Ogma, a high-performance JavaScript graph visualization library. Learn how to query property graphs using SQL/PGQ and seamlessly visualize large-scale networks in the browser using the Ogma Oracle connector. We’ll demonstrate how to move from graph queries to interactive visual exploration, helping developers uncover patterns, investigate connections, and build graph-powered applications efficiently—without complex data pipelines or transformations.

#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

Open Graph Image
www.postgresql.org

PGQ catalog representation and pg_dump support