What I learned from a month with WalShadow on ClickHouse Managed Postgres
Hidehiko ASAHI shares a month of WalShadow private-preview testing, comparing replication latency with ClickPipes and checking data correctness, schema changes, and recovery.
Search headlines, summaries and articles to connect the dots.
Hidehiko ASAHI shares a month of WalShadow private-preview testing, comparing replication latency with ClickPipes and checking data correctness, schema changes, and recovery.
Shipsidekick moved from Neon to ClickHouse Managed Postgres in a single weekend, cutting CPU usage from 100% to 5-10% and making queries about 10x faster.
Ridgeline rebuilt its performance analytics on ClickHouse Cloud, querying decades of Iceberg history alongside recent data so it can serve investment managers 10x larger than before and more than double the customers live on its platform.
At Open House NYC, we showed how ClickHouse Managed Postgres and ClickHouse work as one stack, with a live WalShadow demo replicating Postgres into ClickHouse in under a second, plus the same-week Google Cloud and chdb extension launches.
The chDB Durable Layer keeps agent memory fast to query locally while making its analytical state recoverable across laptops, CI jobs, and short-lived sandboxes.
ClickHouse 26.9 introduces conditional LIMIT boundaries, incremental refreshes for append-only materialized views, disk spilling for DISTINCT, time-limited tokens, and faster min/max/count queries.
Fountain cut analytics latency from three hours to under two minutes and costs by 66% by rebuilding Cue’s data plane on ClickPipes and ClickHouse Cloud.