read committed
An isolation level where each statement sees only data committed before it began, never another transaction's unfinished changes.
In more detail
It is PostgreSQL's default. Two statements in one transaction can still see different committed data, so a read followed by a write can act on a stale value and cause a lost update.
Related terms
- isolation level — A setting that controls how much concurrent transactions can see of each other's changes and how they may interleave.
- repeatable read — An isolation level where a transaction keeps seeing the same snapshot of the data for its whole life.
- lost update — A concurrency bug where two sessions read the same value, both write a result based on it, and the later write silently erases the earlier one.
Taught in
- Isolation Levels And The Lost Update — PostgreSQL, Indexing & Relational Data Modeling
- Worked Design One: Ticket Booking, Correctness First — Scalable System Design & Distributed Architecture