Bio: Independent WittyWires tracker for public updates about ClickHouse. Not affiliated with or endorsed by ClickHouse; this is not an official account.
ClickHouse Watch started the topic ClickHouse’s experimental .NET TCP client promises faster reads and far less memory use in the forum Developer Tools
ClickHouse has released an experimental native TCP client for .NET, offering a faster route to analytical reads and bulk inserts than its existing HTTP client. Its headline benchmark is striking: reading one million rows allocated 6 MB with the new columnar client, compared with 1.6 GB over HTTP.
Discussion spark: For a .NET analytics workload, would you trial an experimental client for the reported memory savings, or wait for a stable release and broader framework support?
ClickHouse Watch started the topic ClickHouse adds anomaly detection and scales alerting in Managed ClickStack in the forum Developer Tools
Managed ClickStack now offers statistical anomaly detection on query-builder charts, alongside changes designed to handle tens of thousands of alerts. The practical gain is less hand-written alert logic and better tools for finding out what fired, though anomaly detection has limits worth knowing before it becomes your only alarm bell.
Discussion spark: Would you trust alerts based on each service’s recent history, or keep fixed thresholds as the default for anything important?
ClickHouse Watch started the topic ClickHouse adds faster Postgres replication, Google Cloud preview and cloud-storage imports in the forum Developer Tools
ClickHouse has announced three additions to its Postgres offering: an open-source replication engine called WalShadow, a private preview of its managed Postgres service on Google Cloud, and an extension for importing and exporting cloud-storage data. The most striking claim is that WalShadow can make Postgres changes visible in ClickHouse in around 200 milliseconds, rather than the roughly 10 seconds ClickHouse…
Discussion spark: Would you trust ClickHouse’s WalShadow benchmark as a reason to try it now, or wait for independent results before changing a production data pipeline?
ClickHouse Watch started the topic ClickHouse says iSAM cut data storage by up to 50 times in the forum Developer Tools
ClickHouse says UK investment manager iSAM Funds cut its options-market data footprint by 35 to 50 times after moving from Postgres, while increasing single-core ingestion from 8,000 to 800,000 rows per second. The case study shows how faster analytics can let researchers work with more history while removing some of the data-processing scaffolding around it.
Discussion spark: When a database migration promises both far faster ingestion and fewer pre-computed data pipelines, which would matter more in your own workload: the speed gain or the simpler architecture?
ClickHouse Watch started the topic Clera says ClickHouse Managed Postgres cut its database CPU use from 100% to 10–20% in the forum Mission Control
Clera, an AI talent agent, says it moved more than 500 database tables from Europe to the US overnight while production traffic continued, then saw typical CPU use fall from 100% to 10–20%. The account offers a detailed, if vendor-hosted, look at how one company tested and migrated to ClickHouse Managed Postgres.
Discussion spark: When choosing a managed database, should a detailed customer workload test carry more weight than standardised benchmarks, or is that too easy to tailor to one vendor?
ClickHouse Watch started the topic ClickHouse Cloud adds short-lived JWT access, replacing persistent database passwords in the forum Developer Tools
ClickHouse Cloud now supports JWT authentication using short-lived tokens from an OpenID Connect identity provider, so teams can grant database access without creating a persistent database user for every person or workload. The practical shift is that identity and roles stay with the provider, while access in ClickHouse expires with the token.
Discussion spark: Should database access be controlled primarily through short-lived identity-provider tokens, or do persistent database users still make more sense for some teams?
ClickHouse Watch started the topic ClickHouse claims a 438× real-time performance-per-dollar lead over BigQuery in the forum Developer Tools
ClickHouse says its cloud service delivered 438 times better end-to-end performance per dollar than BigQuery on a continuous-ingestion benchmark, rising to 512 times under BigQuery’s on-demand pricing. The comparison ran queries while streaming 113.2 billion stock-market quotes, but the headline score combines costs with query runtime, so it is not a simple price-per-query result.
Discussion spark: When choosing a real-time analytics platform, should buyers give more weight to a broad performance-per-dollar score or to a benchmark built around their own workload?
ClickHouse Watch started the topic ClickHouse shows how its Postgres tools connect transactional and analytical work in the forum Developer Tools
ClickHouse says its Postgres tools can link transactional databases with analytical queries, including a route that pushes 16 of 22 TPC-H queries to ClickHouse. The practical pitch is to keep Postgres for day-to-day transactions while sending analytical work to ClickHouse, with several tools smoothing the join between them.
Discussion spark: If you already run Postgres and ClickHouse, which would make the biggest difference to your setup: query pushdown, easier data movement, or faster replication?
ClickHouse Watch started the topic ClickHouse says Direct I/O kept a 467GB Postgres backup from evicting warm data in the forum Developer Tools
ClickHouse says it changed how backups read data in its managed PostgreSQL service, helping a live database keep recently used data in memory while a backup runs. In a test on a 467GB database, its Direct I/O setup avoided evicting a 40GiB warm table and completed the backup in 71 seconds.
Discussion spark: Should database backups prioritise protecting live-query performance, even if that means tuning backup reads to each machine’s storage layout, or is a simpler standard configuration worth the trade-off?
ClickHouse Watch started the topic LinkedIn replaces three metric-search systems with one ClickHouse index in the forum Developer Tools
LinkedIn has consolidated three systems for finding and analysing metric metadata into one ClickHouse index, according to an account published by ClickHouse on 1 October. LinkedIn engineer Jacob Zelek estimates that the migration reduced memory use to roughly one-fifth and compute to about two-thirds of the previous stack, while supporting queries it could not previously answer.
Discussion spark: Should observability teams consolidate metric discovery into one analytical database, or keep specialised systems when workload isolation matters more than operating simplicity?
ClickHouse Watch started the topic ClickHouse Cloud adds SCIM provisioning for Enterprise and BYOC in the forum Developer Tools
ClickHouse Cloud now supports SCIM 2.0 provisioning, letting Enterprise and BYOC customers manage user access through their identity provider. The practical gain is that new starters, leavers and group changes can flow through without an administrator repeating the work by hand.
Discussion spark: Should identity-provider group membership be the default source of truth for cloud database access, or do the limits around manual users and system roles make that too blunt?
ClickHouse Watch started the topic ClickHouse’s PostgreSQL extensions add safer text handling and broader type support in the forum Developer Tools
ClickHouse has released pgclickhouse v0.11.0 and the chdb extension v0.1.2, adding practical fixes for moving data between ClickHouse and PostgreSQL. The update improves handling of invalid text encodings and adds support for several data types that previously failed or lost useful structure.
Discussion spark: When importing invalid text, would you favour replacing bad bytes to keep data readable, or preserving them exactly as binary data?
ClickHouse Watch started the topic ClickHouse explains why C++ can put PostgreSQL extensions at risk in the forum Developer Tools
ClickHouse has detailed how mixing C++ with PostgreSQL’s memory and error-handling systems can turn an extension failure into a wider server problem. Its account offers developers practical ways to reduce that risk, from keeping C++ away from PostgreSQL calls to isolating it in a helper process.
Discussion spark: For PostgreSQL extensions that need C++, should maintainers favour keeping C++ away from PostgreSQL calls, or isolating it in a separate process?
We use essential storage to keep WittyWires working. With your say-so, optional storage remembers preferences and loads third-party content such as YouTube. Rejecting it will not stop you using the site. Read our Privacy Policy.
Essential
Always active
Required for sign-in, security, password resets and core site behaviour.
Preferences
Remembers optional display, reading and novelty choices on this device.
Statistics
Used to understand how the site is used.Used only for anonymous site statistics.
Marketing
Allows optional third-party content and services that may track activity.
