Announcing ClickHouse Managed Postgres on Google Cloud

Summary

ClickHouse Managed Postgres is entering Private Preview on Google Cloud, extending the fully managed, NVMe-backed Postgres service previously launched on AWS. The GCP deployment targets teams wanting Postgres for OLTP and ClickHouse for OLAP in one cloud, avoiding cross-cloud replication, egress costs, and separate networking and compliance management. It uses GCP Local SSD storage, native change data capture through ClickPipes, in-region networking, and pg_clickhouse, which pushes filters, joins, and aggregations to ClickHouse behind a single Postgres connection. Preview capabilities include zonal high availability with two standbys and quorum replication, point-in-time recovery, read replicas, PgBouncer, more than 90 Postgres extensions, monitoring, Query Insights, scheduled upgrades, and infrastructure-as-code support through OpenAPI, Terraform, and clickhousectl. Access is invitation-only via a waitlist, with availability in every GCP region where ClickHouse Cloud runs and hands-on migration support from Cloud SQL, AlloyDB, RDS, Aurora, Neon, or self-managed Postgres.

Takeaways

1. 1

   GCP Local SSD provides physically attached NVMe storage for Postgres; the post says disk latency drops from milliseconds to microseconds and identifies heavy updates, vacuums, WAL spikes, and tail latency under load as workloads that benefit most.

2. 2

   ClickPipes supports an initial load followed by continuous Postgres CDC into ClickHouse Cloud, with replication latency measured in seconds and replication remaining in-region on GCP.

3. 3

   Postgres-to-Postgres ClickPipes offers continuous replication, automated schema migration, and customer-controlled cutover for migrations from Cloud SQL, AlloyDB, RDS, Aurora, Neon, or self-managed Postgres.