Reasoning about Transactional Isolation Levels with Isolde

2026-03-31

AI Summary

This work addresses the challenge of formally comparing the semantic differences among transaction isolation levels. To this end, it introduces Isolde, a tool that, for the first time, automatically constructs counterexamples demonstrating behavioral discrepancies between isolation levels. By modeling transaction executions through formal specifications, Isolde generates execution traces that are permitted under one isolation level but prohibited under another. This approach enables automated verification of isolation-level equivalence and falsification of claimed semantic properties. The method not only reproduces established theoretical results but also uncovers long-standing errors in the literature and previously unknown flaws in the specifications of widely used isolation checkers, thereby significantly advancing the automation and reliability of reasoning about transaction isolation semantics.

Abstract

Most databases can be configured to operate under isolation levels weaker than serializability. These enforce fewer restrictions on the concurrent access to data and consequently allow for more performant implementations. While formal frameworks for rigorously specifying isolation levels exist, reasoning about the semantic differences between specifications remains notoriously difficult. This paper proposes a tool -- Isolde -- that can automatically generate examples that are allowed by an isolation level but disallowed by another. This simple primitive unlocks a range of useful reasoning tasks, including checking equivalence between definitions, and verifying (by refutation) subtle semantic properties of isolation levels. For example, Isolde allowed us to easily and automatically reproduce a famously elusive result from the literature and to discover a previously unknown bug in the alternative specification of a standard isolation level used in a state-of-the-art isolation checker.

Problem

• transactional isolation
• isolation levels
• semantic differences
• serializability
• concurrent access

Innovation

• transactional isolation
• automated reasoning
• formal verification
• concurrency control
• database correctness