A Smooth Sea Never Made a Skillful Sailor

This is a long anticipated third article on optimizing pgbench for CockroachDB. I've been wanting to write a follow up ever since I learned about new improvements in the next release of CockroachDB. 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 coming 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 additional benefits of being more performant at the cost of data anomali...

This is a new series of articles covering short "Today I learned" topics as I peel the layers on CockroachDB. This is meant to resemble release notes. I decided to mix it up with the format for these posts as they may not justify an entire blog. Previous articles Volume 1 Volume 2 Volume 3 Volume 4 Volume 5 Volume 6 Volume 7 Topics Topic 1 $COCKROACH_URL environment variable to save typing with connection strings Saves typing Can store password instead of passing in the prompt every time Pass additional session parameters instead of retyping them all the time I find myself opening multiple command prompts and accessing the same cluster each time. $COCKROACH_URL is a handy trick to save myself time typing the connection string each time. Let's take CockroachDB Free Tier for example, it comes with a long connection string, which by the way also includes a password. One way to approach this is to save the connection string in an environment variabl...