Problemsby GlyphClickHouse queries run too slowly and are hard to tune
2 posts from 2 people2d activeSteady, +1 this weekunverified
Posts per day
The posts behind it
Build with `-ftrivial-auto-var-init=zero`
@groeneai please open a PR against `master` that builds ClickHouse with `-ftrivial-auto-var-init=zero`. Motivation: zero-initializing automatic variables removes a class of bugs where uninitialized stack memory is read or leaked (information disclosure, use of stale pointers)....
RFC: Fragment-aware `EXPLAIN` for distributed plans on stateless workers
...exchange steps inside one tree: no fragments, no instance counts, no dependencies, and no way to tell which hop is blocking. This RFC adds options to `EXPLAIN PLAN` so it build distributed plans for visualization. Today, the `make_distributed_plan` tests pin plans like this one...
Companies and products named
About this problem
Evidence
2 posts from 2 people in 1 place, about 1 a week over 21 days. Mostly on ClickHouse/ClickHouse.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "slow-queries" rule about ClickHouse. First post Oct 6, 2026, latest Oct 26, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
PostgreSQL queries run too slowly and are hard to tune
7 posts from 7 people on Reddit, Stack Overflow, GitHub issues.
Queries run too slowly and are hard to tune
3 posts from 3 people on GitHub issues.
Other ClickHouse problems
ClickHouse users keep filing bugs
Top post: "Tighten seccomp policy for optional kernel interfaces", one of 35 posts from 13 people on GitHub issues.
Trouble with ClickHouse table
Top post: "`SYSTEM RESTORE REPLICA` on a second replica over-bumps the table `metadata` znode version; every later", one of 7 posts from 5 people on GitHub issues.
ClickHouse upgrades break working setups
23 posts from 14 people on GitHub issues.
ClickHouse costs outgrow the value it gives
9 posts from 3 people on GitHub issues.
Trouble with ClickHouse database
Top post: "`DROP NAMED COLLECTION` succeeds while a database uses the collection, and the server then fails to start", one of 6 posts from 2 people on GitHub issues.
Experiments on ClickHouse are hard to reproduce and track
7 posts from 1 person on GitHub issues. Unverified.
ClickHouse error messages are cryptic
5 posts from 3 people on GitHub issues.
Trouble with ClickHouse read
Top post: "ORC: a corrupt PostScript `metadata_length` makes ORC predicate pushdown read `stripe_stats` out of bounds,", one of 4 posts from 4 people on GitHub issues.
Trouble with ClickHouse join
Top post: "Explicit grace_hash now spills at max_bytes_ratio_before_external_join = 0.5 although the build side fits in", one of 4 posts from 3 people on GitHub issues.
Trouble with ClickHouse name
Top post: "SIGSEGV reading a `7z` archive entry without a name", one of 3 posts from 2 people on GitHub issues.
ClickHouse rate limits and usage caps block work
3 posts from 3 people on GitHub issues.
Trouble with ClickHouse return
Top post: "Docs: h3GetResolution incorrectly says invalid indexes return a random value", one of 3 posts from 3 people on GitHub issues.
History