top | item 40938372 (no title) rubenfiszel | 1 year ago Why not call it pg_duckdb ? discuss order hn newest philippemnoel|1 year ago The first version of it was built using Apache DataFusion and we kept the name. We're planning for it to become more than "just" DuckDB in Postgres guillem_lefait|1 year ago Well done !In the github page https://github.com/paradedb/paradedb/tree/dev/pg_lakehouse, DataFusion still appear and probably should be replaced by DuckDB. load replies (1) chrisjc|1 year ago Interested to hear why you switched from DataFusion? load replies (3)
philippemnoel|1 year ago The first version of it was built using Apache DataFusion and we kept the name. We're planning for it to become more than "just" DuckDB in Postgres guillem_lefait|1 year ago Well done !In the github page https://github.com/paradedb/paradedb/tree/dev/pg_lakehouse, DataFusion still appear and probably should be replaced by DuckDB. load replies (1) chrisjc|1 year ago Interested to hear why you switched from DataFusion? load replies (3)
guillem_lefait|1 year ago Well done !In the github page https://github.com/paradedb/paradedb/tree/dev/pg_lakehouse, DataFusion still appear and probably should be replaced by DuckDB. load replies (1)
philippemnoel|1 year ago
guillem_lefait|1 year ago
In the github page https://github.com/paradedb/paradedb/tree/dev/pg_lakehouse, DataFusion still appear and probably should be replaced by DuckDB.
chrisjc|1 year ago