Previous Articles
Previous articles on PgBench and CockoachDB:
- Using PgBench with CockroachDB Serverless
- Optimizing PgBench for CockroachDB Part 1
- Optimizing PgBench for CockroachDB Part 2
Motivation
For the longest time, CockroachDB only supported serializable isolation. In our next release after 23.1, CockroachDB will additionally support read committed isolation. The idea here is that users from other RDBMS tend to face many challenges with application migrations due to the excessive contention stemming from serializable isolation. To ease the migration woes, read committed isolation will provide an easy on-ramp for those applications. Since read-committed isolation is less strict, it has the additional benefit of being more performant at the cost of data anomalies. Today, we're going to take everything we've learned so far in my series and apply it to read committed isolation.