ClickHouse's busy week: cloud identity, OneLake, and Postgres memory safety

ClickHouse bets big on Microsoft

The week's headline is ClickHouse's push into Microsoft's data ecosystem. A native Fabric workload brings sub-second analytics to OneLake data in public preview, backed by dedicated ClickHouse Cloud compute for agents, dashboards, and applications. Alongside it, ClickHouse can now write Apache Iceberg tables directly to OneLake, making the lake a first-class landing zone for analytical workloads. Both arrive under a broader expanded Microsoft collaboration that adds OneLake read and write capabilities and makes ClickHouse BYOC available in the Microsoft Marketplace.

Cloud identity and the operational layers

On the managed side, ClickHouse Cloud picked up SCIM 2.0 provisioning, so an identity provider can create, update, and deprovision organization members and sync group membership to ClickHouse roles automatically — a meaningful change for teams wiring enterprise SSO into their analytics stack. The blog also dug into the internals of its managed Postgres: a piece on why direct I/O backs its backups explains how stripe-sized reads keep backups fast without polluting the page cache and hurting query latency, and a recursive query benchmark compares whether Postgres clusters survive a memory-exhausting query against Cloud SQL, PlanetScale, and Amazon RDS.

Extensions, encoding, and agent memory

The Postgres bridge saw real polish: the latest pg_clickhouse and chdb releases improve character encoding, interval handling, nested data, JSON, and type mappings between the two engines. ClickHouse also published a memory-safety walkthrough for its Postgres extensions, covering the challenges of mixing C and C++ — clean language boundaries and isolated helper processes — which pairs naturally with the extension work above. For the agent crowd, 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.

And behind all of this, ClickHouse kept its release trains moving: a steady stream of stable and LTS updates across the 26.3, 26.7, 26.8, and 26.9 lines, spanning dozens of patches shipped throughout the week.

Dagster goes mobile, Tinybird sets a kernel floor

Dagster's week centered on scale and access: its partitioned declarative automation got faster for assets with long materialization histories, and the UI now has a proper mobile layout with navigation and mobile versions of Home, Jobs, Automation, and the Asset Catalog. Tinybird, meanwhile, flagged a 4KiB page-size requirement for arm64 Tinybird Local images — most distributions are fine, but kernels with larger pages won't start ClickHouse, so arm64 users may need to switch flavors or fall back to amd64.