Search headlines, summaries and articles to connect the dots.
Promoting a standby doesn't stop the old Postgres primary from taking writes. Here's how the control plane behind ClickHouse Managed Postgres fences it on bare metal, AWS and GCP, and why the design is fail-open.
ClickHouse’s new exhaustive cost-based join optimizer safely reorders inner, outer, semi, and anti joins to find the cheapest valid plan.
OpenReplay replaced Postgres with ClickHouse to ingest billions of events and up to 6 TB a day on a single, vertically scaled instance, with sub-second queries and retention handled by a single TTL setting.
ClickHouse Cloud delivered 1,996× better performance per dollar than Redshift Serverless in CostBench. We trace the gap from fresh data arriving to fast answers coming back.
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.
ClickHouse Cloud delivered 438× better performance per dollar than BigQuery in CostBench. We trace the gap from fresh data arriving to fast answers coming back.
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 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.
