DuckDB

DuckDB-Iceberg, one of DuckDB's most popular extensions, received another set of features! In today's blog post, Tom Ebergen and Thijs Bruineman demonstrate the features shipped with v1.5.3: – MERGE INTO – ALTER TABLE – partition transforms – schema properties – V3 support – and more Check out the link in the comments.

We rebranded yesterday from ”DuckDB Labs” to “DuckLabs” and today it's already my first event under the new company name: I'm speaking about DuckDB at Ubuntu Summit 2026. The talk will be live streamed from 11:20 BST / 12:20 CEST. Link in the comments.

I will be speaking at Ubuntu Summit 26.04 on Thursday about DuckDB. My presentation will cover DuckDB at three different deployment models: as a CLI tool, as a portable database, and as a server. I'll explain how DuckDB gives you “as much database as you need” in all these models, enabling you to use a database where you would traditionally reach for other tools. The event is streamed but requires registration – for details, visit https://ubuntu.com/summit

DuckCon #7 is coming up and we're looking for sponsors. We have a lineup of 15 speakers, sharing their experiences with DuckDB. For the first time, the talks will also cover DuckLake and Quack, both from the perspective of the builders and the users who solve real problems with the DuckDB stack. Check out the sponsorship packages on the conference site – link in the comments.

A while back the DuckDB Labs team started a collaboration with LanceDB to bring you an extension that interacts with the Lance lakehouse format from DuckDB. In this post we take the extension for a test drive and confirm that Lance is a very good option for vector and hybrid search workloads. Link in the comments!

The DuckDB team worked with monday.com on a system that's serving complex analytical workloads with trillions of tables. Read their blog post on how they replaced a fleet of MySQL, Cassandra and Redis databases with a single, purpose-built system powered by DuckDB: https://lnkd.in/eg8AYyPH

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: check it out in the comments below.

I had a few people asking me how they can try out DuckLake with Quack as the catalog, so here is a small snippet where we do a few insertions and time-travel. (Google colab link in ze comments)

This Tuesday, we announced Quack, our new protocol that turns DuckDB into a client-server database. Watch this 15-minute segment, recorded at the AI Council, where Hannes explained how Quack works in practice, what stack it's built on, how it performs, and what our long-term ambitions are.

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 comments, give it a spin and let us know what you think. Happy quacking!