Oracle has something like this, and I worked on this project when I was there. Although I was fascinated by the use cases, the adoption was pretty low in the relational world.
I don’t understand why the graph – relational crossover ecosystem doesn’t get more love like this – sometimes I want to explore a different paradigm on my data without installing a completely separate database and performing a migration.
I believe the graph functionality will be a very important new feature for DuckDB. Although the project is still in the research stage, it is incredibly useful for data analysis—especially given the increasing use of semantic relationships in the current internet landscape and within AI agents.
Maybe I’m just silly, but one suggestion – I thought the PG stood for Postgres at first – some sort of cute name might be in order so people don’t get the impression that they have to install this on Postgres + pgduck or something.
SQL/PGQ (Property Graph Queries) is part of the SQL standard as of 2023. I found this project months ago _because_ they included PGQ in their name, I was searching for PGQ implementations.
kuzudb was sunsetted. I think for graph workloads duckdb is best bet, even though this is just a community plugin the upstream duckdb has really robust community doing a lot of heavy lifting and updates.
Recent article about graphdbs including DuckPGQ: https://theconsensus.dev/p/2026/05/29/ladybug-duckdb-and-pos...
Oracle has something like this, and I worked on this project when I was there. Although I was fascinated by the use cases, the adoption was pretty low in the relational world.
https://www.oracle.com/in/database/integrated-graph-database...
I don’t understand why the graph – relational crossover ecosystem doesn’t get more love like this – sometimes I want to explore a different paradigm on my data without installing a completely separate database and performing a migration.
This is super cool!
I believe the graph functionality will be a very important new feature for DuckDB. Although the project is still in the research stage, it is incredibly useful for data analysis—especially given the increasing use of semantic relationships in the current internet landscape and within AI agents.
Maybe I’m just silly, but one suggestion – I thought the PG stood for Postgres at first – some sort of cute name might be in order so people don’t get the impression that they have to install this on Postgres + pgduck or something.
LillipadsDB?
SQL/PGQ (Property Graph Queries) is part of the SQL standard as of 2023. I found this project months ago _because_ they included PGQ in their name, I was searching for PGQ implementations.
SQL/PGQ is part of SQL standard so the naming makes sense.
If you wanted something like this in Postgres, then good news is that PG19 (currently in beta) is adding SQL/PGQ support as well.
how's this comparable to kuzudb & maybe falkordb ?
kuzudb was sunsetted. I think for graph workloads duckdb is best bet, even though this is just a community plugin the upstream duckdb has really robust community doing a lot of heavy lifting and updates.
If you like kuzudb check out https://github.com/LadybugDB/ladybug