ELSEIF
Your brief EB
230 stories from 207 feeds 1242 clusters Refreshed 52 minutes ago next pull 01:18

DATABASES Signal 86

PostgreSQL 19 adds standardized SQL/PGQ graph query syntax through multi-vendor collaboration

PostgreSQL 19 will introduce baked-in SQL/PGQ syntax for property graph queries, bringing standardized graph querying into the relational database without requiring a separate graph DBMS.

WHY IT MATTERS

Teams that need graph queries can potentially avoid adding a dedicated graph database to their stack, querying node-edge relationships directly in PostgreSQL. However, the implementation still lacks indexing optimizations and some syntax features needed to match dedicated graph databases for demanding workloads.

Written by elseif from the cluster below · every claim links back to a source

The three things worth knowing

01

PostgreSQL 19 implements SQL/PGQ, the property graph query standard added to SQL in 2023.

02

The feature resulted from collaboration among multiple large PostgreSQL contributors, including engineers involved with OpenCypher.

03

Indexing add-ons and additional syntax features are still needed before the implementation can displace dedicated graph databases for significant workloads.

THE READ

What the cluster adds up to.

ORIGINAL ANALYSIS

PostgreSQL 19 is set to ship baked-in SQL syntax for querying property graphs, implementing SQL/PGQ from the SQL 2023 standard. This is a departure from the previous approach where graph query capabilities in PostgreSQL were handled through object relational mapping layers rather than native syntax. The release is expected later this month or early October.

The implementation came out of collaboration among several of PostgreSQL's largest contributors, including committers who sit on the SQL standards committee and engineers behind OpenCypher, the open source graph query language. Alastair Turner, a PostgreSQL evangelist at Percona, described it as one of the big multi-vendor collaborations in the project, involving substantial coding and review work across contributors.

The current implementation creates queries across node-edge graphs and some perform well, but Turner acknowledged it still needs one or two additional syntax features before it can displace dedicated graph databases for a significant number of workloads. The more pressing gap is indexing: Turner said indexing add-ons will need to catch up in the next iteration or two to improve performance, meaning teams with heavy graph workloads may not see competitive performance immediately.

Only one feed carried this story, so the framing comes entirely from The Register's reporting and Turner's commentary. The headline's claim that this is a standardized, multi-vendor effort is corroborated by Turner's description of the collaboration, but the caveat about indexing limitations is equally central to the story and should temper expectations for production adoption at scale.

Written by elseif from the cluster below · checked for specifics the sources never contained

THE CLUSTER

Same story, 1 feed.

ORDERED BY FIRST SEEN
www.theregister.com - Articles PostgreSQL 19 connects the dots with standardized graph queries Open ↗