DuckPGQ – A DuckDB community extension for graph workloads

Posted by rzk 8 hours ago

Comments

Comment by zellster 1 hour ago

Recent article about graphdbs including DuckPGQ: https://theconsensus.dev/p/2026/05/29/ladybug-duckdb-and-pos...

Comment by keynesyoudigit 7 hours ago

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!

Comment by keynesyoudigit 7 hours ago

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?

Comment by -pj- 53 minutes ago

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.

Comment by CBLT 6 hours ago

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.

Comment by dzonga 6 hours ago

how's this comparable to kuzudb & maybe falkordb ?

Comment by bfeynman 5 hours ago

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.

Comment by srhtftw 5 hours ago

If you like kuzudb check out https://github.com/LadybugDB/ladybug