DuckDB 2.0.0 LTS 'Cinnamon Teal' released
Archived — this story has rotated out of today’s deck. It is kept here in full.
The gist
DuckLabs released DuckDB 2.0.0 LTS, built from close to 20,000 commits since DuckDB 1.5.
The open-source analytical database now supports shared server access, with support until October 2027.
Background
DuckDB is an open-source analytical database developed by DuckLabs, an Amsterdam-based company. It has been an in-process database since day one, meaning it runs inside an application rather than as a separate server. The Quack protocol, first introduced in DuckDB 1.5.3 in May 2026, lets DuckDB also run in a traditional client-server setup, and 2.0 polishes it. The team says DuckDB 1.0 was about stability and backward compatibility, while 2.0 is above all a feature release.
How it unfolded
- May 2026The Quack protocol appeared as a preview release, in response to users who wanted shared database access.
- Sep 2026The DuckDB team invited community testing of 2.0 development builds.
- Oct 21, 2026DuckLabs announced DuckDB 2.0.0 LTS, codenamed "Cinnamon Teal", described as its biggest feature release so far, built from close to 20,000 commits since DuckDB 1.5.
- Oct 21, 2026The release ships a polished Quack protocol, asynchronous I/O, a first-class VARIANT type, agent mode, triggers and an extensible SQL parser, plus a new default database-file format and a small number of breaking changes.
- Oct 21, 2026DuckDB 2.0 is designated an LTS release with support until at least October 2027; DuckDB 1.4 support runs until late November 2026 and 1.5 support was extended to March 2027.
- Oct 21, 2026CLI and Python clients are already available; other client libraries such as Go, R and Java, and some extensions, can take a few days to release.
Who’s saying what
- Official
- Co-creator Hannes Mühleisen said DuckDB was designed for serverless analysis, but users kept asking for a server, so 2.0 gives them the choice to run in-process or connect to a shared instance.
- Caution
- The DuckDB team advised users upgrading existing deployments, particularly those with multiple DuckDB processes or third-party extensions, to review the migration guidance before updating.