Home / Companies / ClickHouse / Blog / Post Details
Content Deep Dive

What's new in pg_clickhouse v0.10.0: Subqueries, TPC-H Speedups, C Driver, and Aggregates

Blog post from ClickHouse

Post Details
Company
Date Published
Author
-
Word Count
2,568
Company Posts That Month
31
Language
English
Hacker News Points
65
Post removed?
No
Summary

pg_clickhouse v0.10.0 advances ClickHouse pushdown support for PostgreSQL analytic workloads, increasing full TPC-H query pushdown coverage from 12 to 16 of 22 queries and delivering major speedups for queries such as Q17, which fell from 32.7 seconds in an earlier version to 37 milliseconds. The release adds correlated subquery and safe IN/NOT IN pushdown, including safeguards that preserve PostgreSQL’s three-valued NULL semantics despite ClickHouse’s different default behavior, though this correlated-subquery support requires ClickHouse 25.8 or later. It also broadens support for functions, aggregates, partitionwise aggregation, date and time operations, JSON, arrays, window functions, and other SQL features, while making builtin function pushdown explicitly mapped to avoid semantic inconsistencies. Driver changes replace an earlier C++ client with a streaming C-based library, unify binary encoding across HTTP and binary paths, improve memory use, add compression and TLS settings, expand type support, and resolve concurrency and reliability issues. New query and procedure interfaces support arbitrary row-returning queries and effect-only commands against configured ClickHouse servers, while six TPC-H queries remain blocked mainly by join-tree deparsing limitations; future work also includes broader function coverage, UPDATE and DELETE support, and UNION pushdown.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Observability 1 3,175 737 186 -24%
Real-time 1 4,432 1,050 222 -31%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.