Sai Srirampur

A few months ago, we released PostgresBench, an open source benchmark that compares managed Postgres performance across vendors with a transparent, reproducible methodology. It was well received by the Postgres community, and the most common piece of feedback we heard was why we hadn't benchmarked any high availability configurations. Today, we've addressed that, and we're sharing results for HA configurations across those same vendors.

Over the past few years working with thousands of companies on Postgres and ClickHouse, I've watched AI change what applications demand from their databases. Every AI application is a data application: agents generate huge volumes of operational data, and users expect real-time answers built on that data, often in the same request. That changes what applications demand from their databases.

Postgres backups are one of those pieces of infrastructure that should be boring. They sit in the background, continuously archiving WAL files, uploading backups, and making sure that when something goes wrong, recovery is possible. At ClickHouse Cloud, this path is critical. WAL archival is what allows us to preserve durability and recoverability for our Postgres services. WAL-G has been a strong and reliable tool for this job. It is mature, battle-tested, and has served the Postgres community well.