DuckDB, Apache Arrow, SQL, and data engineering.
Written by the people building it.Latest post
A data service can tell DuckDB how long an answer is safe to reuse, so repeated queries can skip another API call. Our benchmarks show when that saves time—and when caching costs more than it saves.
By Query.Farm Team
18 min read
Continue reading: Bringing HTTP’s caching rules to DuckDB functions with VGIOlder posts, newest first. Browse by topic using the Topics menu above.
DuckDB 2.0 brings VARIANT to SQL, storage, and Parquet. Direct Arrow interchange is close, but support still differs across C++, Python, Go, Rust, and Java.
Query Farm's adbc_scanner uses DuckDB 2.0 whole-query pushdown to run supported queries entirely in PostgreSQL. In our benchmark, it was 10–11× faster.
The IP is safe under the DuckDB Foundation, but the Foundation doesn't cut releases — DuckLabs does. What the AWS acquisition changes for people who build on DuckDB, and what Query Farm is doing about it.
Every DuckDB engine release needs its community extensions rebuilt before they install. With data from 1,400+ PRs and a full-catalogue rebuild, we make the case for treating the catalogue as a distribution — and show Haybarn rebuilds it ~2.4× faster.
A DuckDB extension that compiles for WebAssembly has only proven that it compiles. Whether it loads, and whether it actually runs, are separate questions. I built a Node harness to ask them across 124 community extensions. Here's what it found and the fixes that came out of it.
Quack — the new client/server protocol extension for DuckDB — was announced today. It's been built since November 2025, almost exactly as long as I've been building VGI. Here's what's interesting, what's surprising, and where the two projects converge and diverge.
We’ll email you when we publish. Releases, experiments, and things that broke.
Subscribe to the dispatch