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.
A customer saw an extra ~32 ms on simple SELECT queries after idle periods. We traced it to unbatched Native protocol metadata packets overflowing a reset TCP congestion window, reproduced it with network namespaces, and fixed it by batching them.
Executable UDFs are now generally available on ClickHouse Cloud across AWS, GCP, and Azure, with native runtimes, network access, observability, and API and Terraform support.
ClickHouse Managed Postgres uses direct I/O and stripe-sized reads to keep backups fast while protecting the page cache and query latency.
ClickHouse Cloud now supports SCIM 2.0, so your identity provider can create, update, and deprovision organization members and sync group membership to ClickHouse roles automatically.
How do Postgres providers handle a query that exhausts memory? A recursive query benchmark compares query failures and cluster survival across ClickHouse Managed Postgres, Cloud SQL, PlanetScale, and Amazon RDS.
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.