DuckPGQ – A DuckDB community extension for graph workloads

A new DuckPGQ add-on wants to let people do graph-style data analysis inside DuckDB without jumping to a whole new database, and that idea had the comments instantly doing what comments do best: cheering, nitpicking, and tossing out joke rebrands. The loudest reaction was basically, “Finally!” One excited poster said the mix of graph and regular table-based data work deserves way more love, because sometimes people just want to explore their data in a new way without the drama of installing another system and migrating everything. In plain English: fewer moving trucks, more curiosity.

But this being the internet, praise lasted about three seconds before the naming police arrived. One commenter admitted they saw “PG” and immediately thought Postgres, not graph queries, then spiraled into imagining some confusing setup involving totally different software. Their solution? A cuter name. Yes, really. “LillipadsDB” got tossed into the ring, and suddenly the launch had a side quest: is the product cool, or is the name setting people up for confusion?

Then came the comparison crowd, with someone asking how this stacks up against rivals like KùzuDB and FalkorDB. That’s where the mood shifts from “neat research project” to okay, but can it compete? The extension is still openly labeled a work in progress, with bugs and rough edges expected, so the community vibe is a mix of hype, caution, and playful branding chaos.