Skip to content
Free since 2015. Built for the engineers who keep things running.

cat /articles/duckdb-has-an-answer-to-bloated-database-messages.md

Databases

DuckDB has an answer to “bloated” database messages

DuckDB's new Quack protocol streams query results as columnar batches over HTTP, avoiding the repeated overhead that makes older database protocols heavy. It shipped in the DuckDB 2.0.0 LTS release.

The New Stack15 Nov 2026 · 4 min read · summary

article --summary

The summary

Older database protocols were designed before big data and tend to send results row by row, repeating column names and types with every row, which becomes costly when moving large result sets. DuckDB's answer is Quack, an HTTP-based client/server protocol that was previewed in May and reached its first production release in October as part of DuckDB 2.0.0 LTS. Quack sends data in columnar chunks, serializes values efficiently because DuckDB is a vectorized engine, and streams results as the engine emits them, so clients can start working before a query finishes. Developers get features such as the CONNECT statement for querying remote servers, -serve and -connect command-line options, and concurrent multi-client writes under MVCC isolation. According to DuckLabs' Guillermo Sánchez Dionis, the main benefit is a very small memory footprint and minimal server overhead, with more stability improvements expected in upcoming 2.0 patch releases.

Editorial note: This is a summary of an article first published by The New Stack. The full piece is on their site.

Reading now

Topic
Databases
Source
The New Stack
Published
15 Nov 2026
Format
Curated summary

Have a take on this?

Write it up and submit it. It goes on the list once an editor approves it.

Submit an article

articles --latest

Latest articles

New from the blogs we follow and the community.

All articles

newsletter --weekly

DevOps Weekly, minus the noise.

The best reads, new jobs and upcoming events, in one email a week.