Loading post…
ClickhouseAnnouncement
Open House 2026 Day 1: Real-time data without lock-in and what teams can build next
Summary
ClickHouse’s Open House 2026 Day 1 announced updates spanning ClickHouse Cloud, Postgres, distributed query execution, observability, AI agents, and lakehouse interoperability. ClickHouse Postgres entered public beta with local NVMe storage, high availability, S3-backed point-in-time recovery, and a native CDC path into ClickHouse; early benchmarks reported more than 5x the transactions per second of AWS RDS. Multi-stage distributed queries repartition intermediate data between stages to scale joins and high-cardinality aggregations, reducing TPC-H SF100 runtime from 117.6 seconds on one node to 54.7 seconds on eight nodes. Additional launches included a Claude-powered ClickHouse Agents public beta, an AI-enhanced query builder, Monitoring v2, and Langfuse V4’s reported 200x query performance improvement, while the wrap-up framed the releases around real-time systems without lock-in.
Context
AI workloads are creating unpredictable, agent-driven request bursts that need transactional and analytical capabilities. The post says teams have traditionally composed Postgres and ClickHouse by operating them independently and connecting them with custom CDC pipelines, message brokers, and orchestration logic. It also identifies bottlenecks in distributed joins and high-cardinality aggregations, including full hash-table rebuilding on each node and final aggregation concentrating on one coordinator.
Approach / What changed
The announcements add ClickHouse Postgres with local NVMe storage, high availability, WAL archiving, native CDC into ClickHouse, and the pg_clickhouse extension. ClickHouse Cloud also introduces multi-stage distributed query execution that repartitions intermediate data, alongside operational, schema-management, developer, agent, and observability features. Other changes include ClickHouse Agents powered by Claude, lakehouse integrations, and Langfuse V4 performance improvements.
Takeaways
ClickHouse Postgres uses local NVMe storage and supports up to two standby replicas, synchronous commit to the fastest standby, automatic failover, and continuous WAL archiving to S3.
Multi-stage distributed execution repartitions data by join or GROUP BY keys, reducing TPC-H SF100 runtime from 117.6 seconds on one node to 54.7 seconds on eight nodes in early testing.
ClickHouse Agents powered by Claude entered public beta with a native chat experience and no-code agent builder, while the ClickHouse CLI supports agentic workflows.
Source and freshness
- Source
- clickhouse.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.