Skip to content

An isolation level defines which interactions between concurrent database transactions the system permits or prevents.

Different levels trade concurrency and implementation cost against anomalies such as dirty reads, non-repeatable reads, or serialization failures.

Names such as read committed and serializable have database-specific details. Evaluate the actual guarantee, not only the label.