By default, CockroachDB uses the Serializable Transaction Isolation Level, an isolation level that prevents potential data anomalies. This can be useful in real-world scenarios including highly contended environments.
In this video on transaction isolation levels in CockroachDB, Cockroach Labs Technical Evangelist Rob Reid walks through everything you need to know about Read Committed Isolation Levels, locking transactions, guaranteeing consistency, and more.
Further reading:
- Everything you always wanted to know about SQL isolation levels: [ Ссылка ]
- Read committed in CockroachDB (Which transaction level should I use?): [ Ссылка ]
Read Committed Isolation Levels Explained | Consistency in CockroachDB
00:00 Isolation levels in CockroachDB
00:47 Behind Rob's demo
02:06 Testing Postgres | What is a deadlock?
03:20 Testing CockroachDB and enabling pl/pgSQL
04:05 What is a transaction retry error?
04:28 What are read committed isolation levels?
05:11 How does CockroachDB split data? Ranges in CockroachDB explained
05:45 Enabling Serializable Isolation Levels and having the application run retries
06:43 Simulating 1,000 accounts with concurrent users and the impacts on latency
07:07 Closing notes
