← All database systems

Citus is supported by SQLancer — the main repository ships a testing implementation for it. SQLancer is credited with 16 bugs in it, reported between 2020-06-30 and 2026-09-03. Its source is at citusdata/citus.

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 testing

The Citus project maintains its own SQLancer fork, last updated 2020-07-19.

-- -- ISSUE_8468 -- -- Test for GitHub issue #8468: TLP test fail on sqlancer due to -- num_nulls interpreted differently on workers.
src/test/regress/expected/issue_8468.out in the Citus repository states that the project uses SQLancer.
src/test/regress/expected/issue_8468.out last verified 2026-09-13
-- -- ISSUE_8468 -- -- Test for GitHub issue #8468: TLP test fail on sqlancer due to -- num_nulls interpreted differently on workers.
src/test/regress/sql/issue_8468.sql in the Citus repository states that the project uses SQLancer.
src/test/regress/sql/issue_8468.sql last verified 2026-09-13
citusdata/sqlancer is a fork of sqlancer/sqlancer under the Citus project's own GitHub organisation.
/github.com/citusdata/sqlancer last verified 2026-09-13

How the bugs break down

By year reported

2020
2
2023
1
2025
1
2026
4
Year not recorded
8

Who found them

Found by the SQLancer project
1
Found by someone outside the project
7
Reporter not recorded
8

By status

Fixed
8
Open
8

By symptom

Unclassified
16

By technique

Technique not recorded
15
Ternary Logic Partitioning (TLP)
1

Why each bug counts

Listed in the project's own bug repository
8
The reproducer carries SQLancer's generated schema
4
The report names SQLancer
4

Who reported them (6)

Manuel-Neuer1
2
alperkocatas
2
m3hm3t
1
mrigger
1
nukoyluoglu
1
onderkalaci
1

Every bug on record (17)

One row per report, newest first, each linking to the report itself. Rejected reports are marked and are not part of any count above.

Reported Report Status Technique Reporter
2026-09-03 Bug: HAVING `count(*) FILTER (WHERE ref.bool)` is rewritten to `FILTER (WHERE dist.int)` on a two-table dis... open — Manuel-Neuer1
2026-08-24 Bug: DISTINCT over a JSON_EXISTS predicate returns different row counts when the predicate is in WHERE vs. ... fixed — Manuel-Neuer1
2026-02-09 sqlancer test fail with COLLATE used in string concatenation fixed — alperkocatas
2026-02-09 TLP test fail on sqlancer due to num_nulls interpreted differently on workers fixed TLP alperkocatas
2025-01-06 Release 13.0 Improve handling of invalid UTF-8 byte sequences fixed — m3hm3t
2025-01-06 Release 13.0 Error when using unsupported binary operators in queries closed not a bug — m3hm3t
2023-01-29 SQLancer "database is being accessed by other users" fixed — mrigger
2020-07-06 Some check constraints on distributed tables fails fixed — onderkalaci
2020-06-30 ERROR: unrecognized node type: 127 with queries involving COLLATE fixed — nukoyluoglu
— wrongly raised syntax error with INSERT ... VALUES(DEFAULT) open — —
— negative LIMIT error open — —
— error in propogating select queries with casted columns to workers open — —
— Wrong results: WHERE on inheritance parent column drops all rows when cross-joined with a distributed table... fixed — —
— Error in propagating commands to workers in repartition joins open — —
— Columnar ON CONFLICT DO NOTHING fails on tables with PK open — —
— Citus unnecessarily errors out for some expressions with COLLATION on target list open — —
— Citus unnecessarily errors out for some expressions on WHERE clause open — —

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.