🦆 Announcing DuckDB 2.0.0 LTS “Cinnamon Teal” We are proud to release DuckDB 2.0.0, named after the cinnamon teal (Spatula cyanoptera), a striking reddish-brown duck found in the western Americas. 🌎 DuckDB 2.0.0 is the biggest DuckDB feature release so far. It ships a polished version of the Quack protocol, which turns DuckDB into a full-fledged server. It improves performance and lowers costs through supporting asynchronous I/O, a first-class VARIANT type, and a dedicated “agent mode”. It also empowers extension developers with a new SQL parser that allows adding new statements, clauses, and keywords, a new API to build on, and a new mechanism to distribute extensions more easily. In our announcement blog post, we summarize the highlights and then walk through the key changes and give guidance on how to migrate to 2.0. For the complete release notes, see the release page on GitHub⁠. duckdb.org/2026/10/21/announ… #DuckDB

DuckDB 2.0 is coming tomorrow!

DuckLake: The Lakehouse That's Just SQL & Parquet [Talk Python to Me, Ep. 562] How many files does your query read before it reads any data? On some data lakes, you go through JSON and metadata files first, just to learn which Parquet files matter. #DuckLake asks one SQL question instead. The metadata lives in a real database. The data stays in plain Parquet. That's the entire format. With Quack as the catalog, DuckLake handles 200 transactions a second under heavy contention. No other open table format comes close. In this episode of @TalkPython, host @mkennedy talks with @holanda_pe, lead developer for DuckLake at DuckLabs, and Guillermo Sanchez Dionis, who works on both DuckLake and the new Quack protocol – together they discuss all the details of DuckLake, Quack, and more. Watch the episode here or listen wherever you get your podcasts: duckdb.org/library/ducklake-…

🦆🤓 When Denis Hirn implemented DuckDB’s first recursive CTE operator in 2020, correctness determined the design: evaluate the non-recursive term once, then evaluate the recursive term until the next working table is empty. That established the right semantic contract, but reusable runtime state was scoped too narrowly. In the upcoming DuckDB v2.0 release, we assign those scopes explicitly. #DuckDB’s recursive CTE engine now treats recursion as one long-lived computation: it retains eligible epoch-invariant state, chooses execution modes from exact frontier cardinalities and physical work, probes keyed state directly and gives `USING KEY ... UNION` changed-key semantics. Read more in this preview of the forthcoming v2.0 release: duckdb.org/2026/08/25/how-du…

Today, @ducklabs_com is joining @awscloud. The move is expected to be completed by early September. Joining AWS gives DuckLabs the resources and reach to bring DuckDB, DuckLake, and the Quack protocol to many more developers and organizations – and to pursue ideas at a scale that would have been difficult for us to reach alone. The DuckLabs team will remain together in Amsterdam and will continue working for the Duck Stack community as an AWS subsidiary. Most importantly, #DuckDB and the other open source components of the Duck Stack will remain free and open source under the MIT license, with the non-profit DuckDB Foundation continuing its stewardship of the projects. This is a significant moment for DuckLabs and the Duck Stack community. It marks the end of one chapter that we are immensely proud of, and the beginning of another that we believe will take DuckDB much further. Read the full announcement here: ducklabs.com/ducklabs-is-joi… #AWS

Quack, quack! A DuckDB v2.0 preview is here! 🦆 🦆⚡ In this post, #DuckDB co-creators Mark Raasveldt and Hannes Mühleisen preview the headline features of DuckDB v2.0 (expected to arrive this autumn): • DuckDB as a server • Triggers • The VARIANT type • Asynchronous I/O • A new SQL parser • A new storage format • and much more! 🤩 Dive into the details: duckdb.org/2026/08/17/duckdb…

New blog post alert! 🦆 🦆 ⚡ ` Asynchronous I/O in DuckDB: Work, Thread, Work ` by @holanda_pe It doesn't matter how fast query operators are in a database system if we can't pull in the data quickly. For most of DuckDB's history, however, this problem was largely avoided by pruning data early. By pushing down filters and projections, we could ensure that we only read what we actually needed. This worked particularly well because DuckDB primarily ran locally, with its main use case being as a quick-draw database engine for querying data directly from your machine's SSD. But, as usual, things changed. Starting with DuckDB v2.0 – scheduled for fall 2026 – DuckDB will support asynchronous reads of Parquet and CSV files. This significantly speeds up queries when synchronous I/O does not saturate the available bandwidth, as is typical in EC2/S3 compute-storage setups. Read the rest here: duckdb.org/2026/07/31/asynch… #DuckDB

Today, we are releasing DuckDB v1.5.3. This is not an ordinary patch release – it packs many new features as extensions. First, DuckDB v1.5.3 ships our new Quack client-server protocol as an autoloadable core extension. Second, Quack can now also work as a DuckLake catalog. And finally, the AWS and Iceberg extensions made huge strides, along with changes in the HTTPS extension for better proxy support. We wrote a blog post about all these changes and improvements: link in the thread 🧵

Hannes Mühleisen just revealed the Next Big Thing for DuckDB at AI Council 2026: Quack, a protocol that turns DuckDB into a client-server database. True to DuckDB's philosophy, Quack is simple and fast. You can set it up in seconds and it delivers high-performance remote access, turning DuckDB into a full-fledged general-purpose database system. We are very excited to see the possibilities Quack will unlock, from serving multiple concurrent writers to creative architectures with several DuckDB processes talking to each other. The ingenuity of our community never ceases to amaze us and we're certain that we'll see many use cases we did not even think of. For now – follow the link in the thread, give it a spin and let us know what you think. Happy quacking!