What is direct I/O, and why does ClickHouse Managed Postgres use it for backups?
From the source: ClickHouse BlogClickHouse Managed Postgres uses direct I/O and stripe-sized reads to keep backups fast while protecting the page cache and query latency.
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.
How LinkedIn extended ClickHouse from distributed tracing to metric discovery and analytics
LinkedIn expanded its ClickHouse observability stack from distributed tracing to metric discovery and analytics, consolidating 13B+ metrics into one index serving 150k+ queries per minute.
Introducing SCIM Provisioning in ClickHouse Cloud
ClickHouse Cloud now supports SCIM 2.0, so your identity provider can create, update, and deprovision organization members and sync group membership to ClickHouse roles automatically.
pg_clickhouse & chdb updates: Encoding, nesting, and types
The latest pg_clickhouse and chdb extension releases improve character encoding, interval handling, nested data, JSON, and type mappings between ClickHouse and Postgres.
More in Databases
What other companies in Databases are doing. The category page shows who’s active, side by side.
How Jev Uses Meko to Make Code Review Feedback Stick
When a Jev-powered check gets something wrong, and a person corrects it, where does that correction go, and how can you ensure the correction is implemented in future results? This blog explains why a decision model correction should live outside the model, what a system needs to ensure corrections carry into the next request, and the code review check that prevents the system from raising a…
Beyond the return: who controls the business?
A tax return can be correct and still tell the authority too little. The filing identifies the taxpayer but it may not reveal who actually controls the business. Investigations into tax fraud and related financial crime often depend on some… Read more →
What’s New in InfluxDB 3.12: Distributed Compaction, 3x Faster Imports, and More Control
Time series deployments rarely grow the way they were planned. A single-node pilot becomes a multi-node fleet, an afternoon’s worth of test data becomes weeks of backfill that has to land before anyone can query it, and three teams end up writing to a database built for one. InfluxDB 3.11 delivered a higher-performance foundation for complex time series workloads, with significant performance…
Designing Neki for performance
How Neki only decodes the parts of a PostgreSQL result the router actually needs.



