ClickHouse release 26.9
From the source: ClickHouse BlogClickHouse 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.
Read the full story on ClickHouse BlogHave you worked with this?
The story is what was announced. Nobody has discussed it yet, so if it touches your team, a short post about what you’ve seen helps the next reader.
More from ClickHouse
Recent updates from ClickHouse, so you can tell whether this is a one-off or part of a pattern.
ClickHouse appoints Mike Scarpelli, former Snowflake and ServiceNow CFO, to Board of Directors
ClickHouse, a leader in real-time analytics, data warehousing, observability, and AI/ML, today announced the appointment of Michael Scarpelli to its Board of Directors
How Fountain rebuilt its data plane on ClickHouse Cloud to power Cue, the Frontline Superintelligence
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.
Postgres on NVMe: performance and the convergence of transactions and analytics
See how local NVMe transforms Postgres transaction performance—and why ClickHouse remains essential for fast analytics as workloads scale.
More in Databases
What other companies in Databases are doing. The category page shows who’s active, side by side.
How to add hybrid search to a Postgres app with Pinecone in 2026
Add hybrid search to a Postgres app with Pinecone: full-text and vector search in one index, Postgres as the source of truth. Built around a snack shop example.
When to choose x86-64 vs aarch64
ARM and x86 can give you different performance at the same vCPU count. Here's what differs, what to measure, and how to choose.
Who controls your intelligence analysis platform?
Over the years, I’ve seen two broad philosophies emerge for building an intelligence analysis platform. One concentrates knowledge and capability inside the vendor. The other builds them inside the customer’s own team. The distinction matters more as the platform grows.… Read more →
How to Solve the Agent Handoff Problem
If your agents hand work to each other, or to a teammate's agents, this is the difference between the next agent building on a decision and rebuilding a dead end. Discover how to solve the agent handoff problem with Meko, the agent-native context engine for multi-agent AI systems. The post How to Solve the Agent Handoff Problem appeared first on Yugabyte .




