Articles

Answers to the question you searched for, with the numbers attached.

Tip1 to 3 min Note3 to 6 min Deep dive8 min and up

Format All Tip Note Deep dive

Problem All bytes per row clickhouse clickhouse codecs compression ratio connection pool disk budget doubledelta node-postgres postgres reliability sort key t64 timeouts

Deep dive

Choosing ClickHouse codecs per column profile

A 100-billion-row table at 4.37 bytes per row. The codec behind each column, the number it produced, and the loop to repeat the test on your own data.

measured ▸ 269.6x on the sort-key timestamp · 4.37 bytes per row over 100.78 billion rows

clickhouseclickhouse codecscompression ratiosort keybytes per rowdoubledeltat64disk budget

Oct 2026 7 min
Tip

query_timeout doesn't cancel anything

In node-postgres, query_timeout gives up on the client side only. The query keeps running on the server and the connection stays busy. Use statement_timeout and TCP keepalive.

measured ▸ query_timeout: error after 1 s, query still running on the server · statement_timeout: error 57014, 0 left running

postgresnode-postgresconnection pooltimeoutsreliability

Oct 2026 3 min