What it does
histcheck is an Elle-style offline checker. Given a recording of concurrent transactions, it builds a dependency graph, finds cycles, classifies them against the standard anomaly taxonomy and gives a verdict for read committed, snapshot isolation, serializable and strict serializable. The engine's tests use it; it is not part of the server.
How it works
A history lists each transaction with its invoke and complete times and what it read and wrote. The checker infers write-write, write-read and read-write edges plus real-time edges, finds cycles, and names each one: G0, G1a, G1b, G1c, G-single, G2-item, lost update or a real-time-order violation. It returns a minimal witness cycle for each failing model.
It is engine-agnostic and depends on nothing else in the workspace. The engine's integration tests record concurrent optimistic-transaction workloads and pass the histories to it.
Where you reach it
- Library
histcheck::classify::check, ConsistencyModel (used by engine tests; not part of the server)
Limits
- A prototype for evidence-gathering, built independently from the published definitions. It is not a product feature.
- It judges the histories it is given. It does not prove properties of unrecorded executions.
Evidence
- TestsCovered in the engine repository by about 30 checker tests (anomaly classes, serial-history properties) and by the engine's own history tests that use it
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
This is not available in the preview. Request a preview to discuss the current scope.