nitpick: this library requires consumer give io callbacks (potentially through the included clickhouse-client.h header), or use the sans-io interface (which clickhouse-c-rs[1] uses to implement tokio layer), which makes it capable of talking over native tcp protocol, http, or stdin/stdout (clickhouse local). ClickHouse has both native protocol[2] & native format[3]
With pg_clickhouse this doubled throughput while reducing memory usage. The original motivation was to supplant clickhouse-cpp to remove C++ from codebase (c++ runtime doesn't play nice with postgres runtime)
Nice not needing text parsing for postgres/clickhouse value conversions
nitpick: this library requires consumer give io callbacks (potentially through the included clickhouse-client.h header), or use the sans-io interface (which clickhouse-c-rs[1] uses to implement tokio layer), which makes it capable of talking over native tcp protocol, http, or stdin/stdout (clickhouse local). ClickHouse has both native protocol[2] & native format[3]
1: https://github.com/ClickHouse/clickhouse-c-rs
2: https://clickhouse.com/docs/resources/develop-contribute/nat...
3: https://clickhouse.com/docs/resources/develop-contribute/nat...
It sounds interesting, but what are the actual advantages compared to a standard HTTP client? At what data volume does performance parity begin?
With pg_clickhouse this doubled throughput while reducing memory usage. The original motivation was to supplant clickhouse-cpp to remove C++ from codebase (c++ runtime doesn't play nice with postgres runtime)
Nice not needing text parsing for postgres/clickhouse value conversions
& you can use this format over http