ClickhouseAnnouncement
September 2026 newsletter
Summary
The September 2026 ClickHouse newsletter gathers product updates, community contributions, technical articles, and upcoming events. Its main release coverage describes ClickHouse 26.8, including custom HTTP handlers, dynamic query filtering, pipelined SQL through the |> operator, current-user query logging, a URL database engine, and Japanese and Chinese text-index tokenizers. Other featured developments include On-Demand Compute in private preview with a cost-based optimizer and distributed query execution, PromQL and a TimeSeries engine in private preview, AI Functions, and Postgres integrations such as WalShadow and Managed Postgres on Google Cloud. The issue also reports CostBench’s first end-to-end performance-per-dollar results, explains replication-queue diagnosis, notes 57 breaking changes since 26.3, and lists training, webinars, roadshows, and other events.
Context
A monthly ClickHouse newsletter covering the 26.8 release, product previews, community work, technical posts, Postgres developments, benchmark results, and scheduled events.
Takeaways
ClickHouse 26.8 adds custom HTTP handlers, dynamic query filtering, the |> transformation operator, current-user query logging, a URL database engine, and Japanese and Chinese text-index tokenizers.
On-Demand Compute is in private preview with dedicated workers, a new cost-based optimizer, and a distributed query execution framework for intensive workloads.
CostBench measures performance-per-dollar under continuous ingestion across ClickHouse Cloud, Snowflake, BigQuery, and Redshift Serverless, including the cost of keeping data fresh for queries.
FAQ
What does ClickHouse 26.8 add?
The release adds custom HTTP handlers and dynamic query filtering for streaming HTTP APIs, plus the |> operator for transformation sequences. It also includes current-user query logging, a URL database engine, and Japanese and Chinese tokenizer support for the text index.
What is included with On-Demand Compute?
On-Demand Compute is in private preview and lets intensive workloads run on dedicated ClickHouse workers. It includes a cost-based optimizer and a distributed query execution framework.
Does a non-empty replication queue mean a replica is broken?
Not necessarily. The newsletter’s replication-queue article explains how to investigate backlogs with the system.replicas and system.replication_queue system tables and why a queue can be non-empty without indicating that something is wrong.
Source and freshness
- Source
- clickhouse.com
- Published
- Added to Yomu
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.