Xerox
Community Discussion - Open
Myself and Peter Eisentraut are working on implementing SQL/PGQ (SQL:2023) standard into PostgreSQL [1]. With this feature, PostgreSQL users will be able to query their relational data as graph data in PostgreSQL itself. Today, users can use PostgreSQL as a graph database using extensions like Apache AGE, specialized forks like AgensGraph, or algorithmic libraries like pgRouting.
This developer meeting aims to bring graph database experts in the PostgreSQL ecosystem together. The communities around the products which are already used in the field have an understanding of the customer needs which can be used to prioritize the next set of features in SQL/PGQ core implementation. These products in turn can benefit from adopting SQL/PGQ as their underlying implementation. Through this symbiosis the wider ecosystem can thrive. Specifically the relationship between Apache/AGE and SQL/PGQ implementation in core is expected to evolve similar to the relationship between pg_partman and in-core partitioning. We will discuss various collaboration options and come up with a mutually beneficial roadmap.
We expect the following developers and field experts to participate in the meeting. o. Peter Eisentraut and Ashutosh Bapat, authors of SQL/PGQ implementation o. Junwang Zhao (Apache/AGE), Henson Choi (AgensGraph), and reviewers of SQL/PGQ implementation o. John Gemignani, committer Apache/AGE o. Representatives from EdgeDB and pgRouting. Specific names need to be finalized.
We expect the feature to be available in PG 19 or merged upstream earlier in PG 20. The agenda of the meeting doesn’t change much irrespective of the outcome. It will influence the development of the feature after the first version is committed.
[1] https://www.postgresql.org/message-id/a855795d-e697-4fa5-8698-d20122126567%40eisentraut.org
