← All database systems

SeekDB has no testing implementation in the main SQLancer repository. SQLancer is credited with 3 bugs in it, reported between 2026-04-16 and 2026-08-11. Its source is at oceanbase/seekdb.

How the project uses SQLancer

Official testing

The SeekDB project maintains its own SQLancer fork, last updated 2022-12-05.

oceanbase/sqlancer is a fork of sqlancer/sqlancer under the SeekDB project's own GitHub organisation.
/github.com/oceanbase/sqlancer last verified 2026-09-06

How the bugs break down

By year reported

2026
3

Who found them

Found by someone outside the project
3

By status

Fixed
1
Open
2

By symptom

Unclassified
3

By technique

Technique not recorded
2
Ternary Logic Partitioning (TLP)
1

Why each bug counts

The reproducer carries SQLancer's generated schema
2
The report names SQLancer
1

Who reported them (3)

chyujing
1
cms-cms
1
footka
1

Every bug on record (3)

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-08-11 Plan cache memory usage far exceeds limit and memory continues to grow after SQLancer stress test open — chyujing
2026-08-04 seekdb: Result size mismatch for GROUP BY ... WITH ROLLUP + HAVING partitioned TLP (RIGHT JOIN null-extende... open TLP footka
2026-04-16 Fix memory allocation failure (errcode=-4013) during vector benchmark with async index fixed — cms-cms

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.