DuckDB 2.0.0 LTS “Cinnamon Teal”
- ID
- 38163
- Status
- summarized
- Published
- 21 Oct 2026, 10:01 PM
- Fetched
- 22 Oct 2026, 9:28 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://duckdb.org/2026/10/21/announcing-duckdb-200
- Source URL
- https://hnrss.org/best
Summary
- Score
- 8.0
- Created
- 22 Oct 2026, 9:29 AM
- Tags
- Audience
- developersvibe_codersdatabase_learnersai_ml_learnersai_agent_users
What happened
DuckDB 2.0.0 LTS, codenamed "Cinnamon Teal", is out with close to 20,000 commits since 1.5 and is supported until at least October 2027. Headline features include a polished Quack client-server protocol with a new CONNECT statement for attaching and switching to a remote database in one command, asynchronous I/O, a first-class VARIANT type, agent mode, triggers, and an extensible SQL parser. It is explicitly a feature release with breaking changes and a migration guide, and only the CLI and Python clients are available immediately — Go, R, Java and some extensions can lag by a few days.
Why it matters
If you pin DuckDB anywhere, the support calendar just shifted: 1.4 runs to late November 2026, 1.5 was extended to March 2027 (now effectively LTS too), and 2.0 runs to at least October 2027 — so decide which line you standardise on before the November 2026 cutoff. Because 2.0 carries breaking changes and the Go/R/Java bindings ship days later, upgrading production pipelines this week risks a version mismatch between your Python/CLI tooling and your service bindings; read the migration notes first. The new CONNECT statement and Quack protocol also mean you can now attach a remote DuckDB over its native protocol, which changes whether you need a separate warehouse for small multi-service setups.
Discussion angle
With Quack and the CONNECT statement, DuckDB now has a real server mode — where does that move the line between DuckDB and Postgres/SQLite in your stack, and which of your projects would you actually switch?