Databricks has unveiled a significant performance upgrade for managed Postgres, leveraging its lakebase architecture Postgres to deliver up to five times faster write throughput. This advancement tackles a critical bottleneck in high-scale Postgres applications by fundamentally rethinking how durability is handled.
Traditional Postgres durability mechanisms introduce overhead. To prevent data corruption during crashes, Postgres logs entire data pages before writing them to disk, a process known as full page writes (FPW). On write-heavy workloads, this can inflate Write-Ahead Log (WAL) volume by up to 15 times, becoming the dominant cost and limiting performance.
Eliminating the 'torn page' problem
The lakebase architecture separates compute and storage. In this model, compute nodes are stateless, streaming WAL records to a distributed quorum of safekeepers. This design inherently eliminates the risk of torn pages on local disk, as there is no local data directory.
However, simply disabling FPW creates a new challenge: read performance. Without periodic full page images, reconstructing data pages for reads could involve replaying an unbounded chain of small changes, drastically increasing latency and resource consumption.
Image generation pushed to storage
Databricks solved this by moving intelligence to the storage layer. The pageserver now reconstructs pages by finding the latest materialized image and replaying WAL deltas. Crucially, it generates new full page images only when a page accumulates a significant number of delta records without an intervening image. This 'image generation pushdown' is driven by actual page changes, not the arbitrary Postgres checkpoint process.
