Post

Why we’re moving our warehouse off DuckDB

PostHog is rebuilding its hosted warehouse around Trino and its own HogLake table format after finding that single-node sizing and DuckLake catalog operations became difficult at its scale.

It reports a 2 PB test deployment with roughly a trillion rows and 15.3 million snapshots; cleaning stale catalog statistics temporarily sped writes by 30–50×. The company also found scaling pgwire connections and client compatibility costly. These are observations from its particular hosted workload, not a general verdict on DuckDB.