← All database systems
ClickHouse is supported by SQLancer — the main repository ships a
testing implementation for it.
SQLancer is credited with 48 bugs in it, reported between 2020-06-24 and
2026-09-12.
Its source is at ClickHouse/ClickHouse.
A further 1 report was
filed and rejected by the developers as invalid or duplicate. Those are kept
in the dataset for transparency and are excluded from every count here.
How the project uses SQLancer
Official ci
The ClickHouse project runs SQLancer from its own repository (.github/workflows/nightly_sqlancer.yml).
PYTHONUNBUFFERED=1 python3 -m praktika run 'Dockers Build (amd)' --workflow "NightlySQLancer" --ci --timestamp
.github/workflows/nightly_sqlancer.yml in the ClickHouse repository invokes SQLancer..github/workflows/nightly_sqlancer.yml
last verified 2026-09-13
Official testing
The ClickHouse project maintains its own SQLancer fork, 209 commit(s) ahead of upstream, last updated 2026-09-02.
# `clickhouse/sqlancer-test` image (ci/docker/sqlancer-test/Dockerfile) installs
ci/jobs/sqlancer_pp_job.sh in the ClickHouse repository invokes SQLancer.ci/jobs/sqlancer_pp_job.sh
last verified 2026-09-13
# `ci/docker/sqlancer-test/Dockerfile`), but that image is only rebuilt when its
ci/jobs/sqlancer_job.sh in the ClickHouse repository invokes SQLancer.ci/jobs/sqlancer_job.sh
last verified 2026-09-13
ClickHouse/sqlancer is a fork of sqlancer/sqlancer under the ClickHouse project's own GitHub organisation, 209 commit(s) ahead of upstream./github.com/ClickHouse/sqlancer
last verified 2026-09-13
How the bugs break down
By year reported
- 2020
-
5
- 2021
-
4
- 2022
-
2
- 2023
-
2
- 2024
-
2
- 2025
-
3
- 2026
-
29
- Year not recorded
-
1
Who found them
- Found by the SQLancer project
-
7
- Found by someone outside the project
-
41
By status
- Fixed
-
36
- Confirmed
-
1
- Open
-
11
By symptom
- Unclassified
-
48
By technique
- Technique not recorded
-
32
- Ternary Logic Partitioning (TLP)
-
11
- Differential Query Plans (DQP)
-
2
- Non-optimizing Reference Engine Construction (NoREC)
-
2
- Constant-Optimization-Driven Testing (CODDTest)
-
1
Why each bug counts
- The report names SQLancer
-
26
- The reproducer carries SQLancer's generated schema
-
10
- The report names a SQLancer oracle
-
8
- Filed by someone who runs SQLancer campaigns
-
4
Who reported them (8)
- qoega
-
20
- fm4v
-
12
- wanteatfruit
-
3
- Algunenano
-
2
- alexey-milovidov
-
2
- suyZhong
-
2
- zlareb1
-
2
- 123lpygithub
-
1
Every bug on record (49)
One row per report, newest first, each linking to the report itself. Rejected
reports are marked and are not part of any count above.
Every figure on this page is computed from
_data/impact/.
The attribution policy
explains what has to be true for a bug to be counted.