DuckDB

#sponsors" target="_blank" rel="nofollow noopener">duckdb.org/events/2026/06…

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 thread 🧵.

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: duckdb.org/2026/05/21/tes…

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 🧵

This Tuesday, we announced Quack, our new protocol that turns DuckDB into a client-server database. Watch Hannes' talk, recorded at the AI Council, where he 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 thread, give it a spin and let us know what you think. Happy quacking!

Δ duckdb.org/2026/05/07/del…

The Delta and Unity Catalog extensions in the latest DuckDB release come with a fresh set of features and have shed their experimental labels. In today's blog post, Ben Fleis walks you through the key improvements: ✍️ You can now write Delta tables with DuckDB. Multiple inserts within a transaction produce a single atomic version in the Delta table. 🤝 The Unity Catalog unlocks multi-writer access. DuckDB and other clients such as Spark can now perform writes alongside each other with the catalog handling concurrency control. ⏪ You can use the coolest feature of data lake formats: time travel. This lets you query any Delta table at a specific historical version. Thanks to incremental snapshot loading, this is fast even across large Delta logs. Read the full blog post for more – link in the thread 🧵

We're excited to announce the program of DuckCon #7 Amsterdam! The event will start with the “State of the Duck” talk, covering DuckLake v1.0 and the super-secret next big thing for DuckDB – something we cannot tell you more about yet as it will be released next week! We'll continue with six regular talks covering use cases, technologies built with DuckDB and DuckLake, and a talk on how Spotify uses DuckDB to analyze their listening history. The program also features six lightning talks, including one on how the Toyota Gazoo Racing World Rally Team built an application with DuckDB. Finally, we'll have drinks and snacks so you'll have ample time to socialize with the flock! For the full program and registration, follow the link in the thread.

Today is Star Wars day! We are taking the opportunity to tell you about our journey, not across galaxies, but through the process of creating DuckLake dataframe clients with the use of a clanker 🤖. Read more at ducklake.select/2026/05/04/duc…

A great short post on DuckDB: peterdohertys.website/blog-posts/dab… We certainly didn't expect “interactive installations and art projects” among the list of use cases, but we agree with the author that DuckDB could definitely work in that context too 🎨

Today is your last chance to submit a talk proposal to DuckCon #7. The submission form is lightweight, so it shouldn't take long. If you're in doubt whether your talk idea fits, drop us a DM and we are happy to discuss it further!

@_miguelangel You can use the AUTOMATIC_MIGRATION flag: #connecting-to-an-older-ducklake" target="_blank" rel="nofollow noopener">ducklake.select/docs/stable/du…

@duckdb Is there any guide for migrating to 1.0?

We are happy to release DuckLake v1.0, a production-ready lakehouse format specification. Its reference implementation, the ducklake DuckDB extension, is available as of today in DuckDB v1.5.2. Since releasing the DuckLake manifesto in May 2025, we have seen massive adoption, with DuckLake deployed in production at multiple organizations, third-party clients supporting DuckLake, and even an upcoming O'Reilly book. DuckLake v1.0 ships many new features (inlining, partitioning, bucketing, type system improvements) and guarantees backwards-compatibility in the specification.

We are hosting the next edition of our community conference, DuckCon, in Amsterdam on June 24. The registration is already open and you can submit your talk proposals until next Wednesday. Looking forward to your submissions and seeing the flock in the summer!

The Register published a report on DuckLake v1.0: > In a blog post accompanying the 1.0 launch, Pedro Holanda, DuckDB Labs principal engineer, said the company's benchmark shows 926× faster queries and 105× faster ingestion when compared to Iceberg, the open table format. > "When I wrote the blog post about saying we had the 1,000x difference, I felt like, 'Oh, some people are gonna get angry,' but no one got angry. They're like, 'This is a real problem.' I even had someone say they were cheating with the architecture. That's the whole point: cheating with a better design," he told The Register. As bonus content, here's a snippet from our recent podcast where Mark Raasveldt and Pedro Holanda explain how data inlining works.

We heard that a specification looks more serious if it's served as a PDF. Well, you can read the DuckLake documentation as a PDF now (blobs.duckdb.org/docs/ducklake-…)! This document covers both the specification and the DuckDB extension's usage.

YouTube: youtube.com/watch?v=7Su0aV… Spotify: open.spotify.com/episode/6Xe6iC…

Yesterday, we released DuckLake v1.0 and also published a podcast where Pedro Holanda and Mark Raasveldt talk about the DuckLake – going into quite some technical details on compaction and the challenge of long-running data lakes. Listen to the full conversation on YouTube or Spotify! Links in the 🧵