4 ms·
> Higher isolation levels add read locks that can block concurrent transactions. Not in postgres. REPEATABLE READ doesn't add any locks, and SERIALIZABLE adds
by anarazel 9y ago
> Higher isolation levels add read locks that can block concurrent transactions.
Not in postgres. REPEATABLE READ doesn't add any locks, and SERIALIZABLE adds locks, but they're optimistic. So blocking isn't something you're going to see - the relevant thing to measure is going to be the rate of transactions being rolled back due to serialization failures.
- barrkel 9y agoSure, but the article isn't about postgres.
- anarazel 9y ago> Sure, but the article isn't about postgres. Indeed. But your point was: > Higher isolation levels add read locks that can block concurrent transactions. Which isn't generally true, given the example of postgres.
- anarazel 9y ago> Sure, but the article isn't about postgres. Indeed. But your point was: > Higher isolation levels add read locks that can block concurrent transactions. Which isn't generally true, given the example of postgres.