● Covered by 2 sources · 3 reportsMedium impact3 neutral
DuckDB v2.0 "Cyanoptera" to Introduce Server Mode, New SQL Parser, and Storage Format
Key points
- DuckDB v2.0 "Cyanoptera" will be released this fall.
- It includes a new SQL parser and default storage format.
- A stable client/server mode is introduced via the 'quack' extension.
- The 'CONNECT' statement enables connections to remote databases.
- The new parser replaces a PostgreSQL-derived parser.
- The new parser allows for runtime extensions.
- DuckDB v2.0 is a major architectural evolution.
- DuckDB v2.0 has over 10,000 commits since version 1.5.
- The 'quack' extension enables any DuckDB instance to run as a daemon.
- The networking layer relies on DuckDB's unified binary format.
DuckDB v2.0 "Cyanoptera" Release
DuckDB v2.0, named "Cyanoptera" after the cinnamon teal, is set for release this fall. This major version update includes a new SQL parser, a new default storage format, and a reworked C API. The release incorporates over 10,000 commits since v1.5.
Introduction of Client/Server Mode
A key feature of v2.0 is the stabilization of its client/server mode, which has been a persistent request from users. The 'quack' extension, previously in preview, will graduate to stable, enabling any DuckDB process to serve its databases over a network. Other DuckDB instances can then connect and route queries using the new 'CONNECT' statement.
Enhanced Remote Database Connectivity
The new 'CONNECT' statement replaces previous workarounds for remote queries. It allows a DuckDB session to connect to any remote database that supports it. Additionally, a new remote pushdown optimizer (#22914) will enable SQL queries to be shipped directly to external databases like PostgreSQL and MySQL, rather than pulling entire tables over the network.
Updates
- DuckDB v2.0 is a major architectural evolution.
- DuckDB v2.0 has over 10,000 commits since version 1.5.
- The 'quack' extension enables any DuckDB instance to run as a daemon.
- The networking layer relies on DuckDB's unified binary format.
- The new parser replaces a PostgreSQL-derived parser.
- The new parser allows for runtime extensions.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
How outlets covered it
DuckDB Labs released a preview of DuckDB v2.0, codenamed "Cyanoptera," which adds native client/server capabilities and a stable C API for extensions. This update expands DuckDB's use cases beyond embedded applications to distributed network topologies and improves ecosystem stability.
DuckDB v2.0 introduces a new PEG-based SQL parser, replacing its previous PostgreSQL-derived parser. This change aims to simplify the evolution of DuckDB's SQL syntax and allow for runtime extensions, improving the database's adaptability.
DuckDB v2.0, codenamed "Cyanoptera," is scheduled for release this fall, bringing a new SQL parser, a new default storage format, and a reworked C API. The update's most significant feature is the introduction of a stable client/server mode, allowing DuckDB processes to serve databases over a network and connect to remote databases like PostgreSQL and MySQL.