International
The Morning Dev

Only the news worth knowing

‹
 

Release

DuckDB just shipped its biggest release ever. Its own team says not to run it in production just yet.

The New Stack · By Jennifer Riggins ·

DuckDB just shipped its biggest release ever. Its own team says not to run it in production just yet.

The Brief

  • DuckDB shipped its biggest release to date, DuckDB 2.0, in October.
  • Some storage changes mean older DuckDB versions may be unable to read files written by 2.0.
  • The DuckDB team advises against running 2.0 in production for now.

Why it matters

Files written by DuckDB 2.0 may not open in older versions, so upgrading can lock data into the new format. Teams that depend on DuckDB storage need to plan around that before adopting it.

Who’s affected

  • Teams running DuckDB in production
  • Developers storing data in DuckDB files

What to do

  1. Do not run DuckDB 2.0 in production yet, as the DuckDB team advises.
  2. Keep older DuckDB versions able to read your files before upgrading.

DuckDB’s developers had more than a few ideas for improving how their database stores data, and some of those ideas went far enough that older versions might no longer be able to read files written by the new one. That was enough to make October’s release DuckDB 2.0. Now the team…

How do you feel about this?

0 Comments