DuckDB v2.0 Preview: Server Mode and Major New Features
Original: A Preview of DuckDB v2.0
Why This Matters
DuckDB's shift to client/server mode broadens its applicability from single-user analytics to multi-tenant production deployments.
DuckDB v2.0 'Cyanoptera' is set for release this fall, featuring over 10,000 commits since v1.5. Key additions include native client/server mode via the Quack protocol, a new SQL parser, new default storage format, triggers, VARIANT type, and async I/O.
DuckDB v2.0, codenamed 'Cyanoptera' after the cinnamon teal duck, is scheduled for fall 2026 and represents the project's first major version bump. Built from over 10,000 commits since v1.5 (released March 2025), it includes several breaking changes: a new SQL parser, a new default storage format, a reworked C API, and a small number of deliberate API changes.
The headline feature is DuckDB as a server. The 'quack' extension, previewed before DuckCon #7, graduates to stable in v2.0. It enables any DuckDB process to serve databases over a network using the new CONNECT and DISCONNECT SQL statements, replacing the earlier remote.query() workaround. CONNECT also supports remote pushdown to PostgreSQL and MySQL, routing SQL directly to those engines rather than pulling data over the wire.
DuckDB has supported full MVCC and transaction isolation since its inception, but the client/server architecture now makes this accessible to multi-tenant and long-running deployments. v2.0 also improves observability with a reworked metrics and logging layer. Additional upcoming features include triggers, a VARIANT type, asynchronous I/O, and more, previewed at DuckCon #7.