At PostHog, writing to a single DuckLake table took more than three minutes. Most of that time went to statistics for tables that no longer existed.
That detail, from PostHog's post about moving their warehouse off DuckDB , is the most useful thing I've read about DuckDB's limits at scale this year. It also makes "DuckDB doesn't scale" look like a lazy takeaway, because the query engine held up fine. What broke was DuckLake's metadata layer, the one-machine sizing model, and the Postgres wire protocol, once all of them were serving a multi-tenant cloud product at 2 PB. PostHog is moving the warehouse to its own build of Trino.
I'll go through their numbers first. Further down are two SQL queries that tell you whether your own DuckLake catalog is heading the same way, and a checklist for when staying on DuckDB is still the right call.
Five months from DuckDB launch to Trino migration
On June 29, 2026, PostHog published Why we rebuilt our data warehouse on DuckDB over ClickHouse . They had sound reasons.…