Lesson 4.1
Transactions and isolation levels
Isolation decides which concurrency anomalies you can still see. Read committed is the default, and it permits more than most people assume.
8mIntermediate6,361 students
Sign in to watch this lesson
Browsing is free. Create an account to play videos and track your progress.
Overview
Isolation decides which concurrency anomalies you can still see. Read committed is the default, and it permits more than most people assume.
What this lesson covers
- Keep transactions short and correctly scoped
- Compare read committed, repeatable read, and serializable
- Avoid deadlocks by ordering access consistently
This lesson sits in Operating Postgres, part of PostgreSQL for Developers. It assumes what came before it and leads directly into the next lesson in the module.
In this lesson you will:
- Keep transactions short and correctly scoped
- Compare read committed, repeatable read, and serializable
- Avoid deadlocks by ordering access consistently