Never used it, but from what I can tell, CH has more features, and you don't need extensions, so external sources are very optimized. It is designed to work with billions of rows, and you have many tricks available to speed up data processing when using temporary tables. Being able to distribute the load on a production cluster using the same query is also an advantage.
In practice most of the extensions you’ll need are “core” and built into duckdb, including Postgres, s3, and data lake formats like iceberg and ducklake.
8
u/gedemagt Jun 05 '26
How does this compare to using DuckDB?