Handling Contention with PostgreSQL

Diana Hsieh
Oct 23, 2017 · 2 min read

Understanding how concurrency is achieved under the hood is pretty important for anyone using databases since it impacts things like isolation guarantees and performance. I had originally wanted to share a comparison of how CockroachDB and PostgreSQL use MVCC differently to handle concurrency. However, the CockroachDB implementation had too many additional bells and whistles, and it would have made this post too long. So for now, here’s a quick overview of PostgreSQL’s MVCC model. It’s a complicated topic, so let me know if you see anything I should fix on Twitter @Dianasaur323!

Image for post
Image for post
Image for post
Image for post
Image for post
Image for post
Image for post
Image for post
Image for post
Image for post

Learning with Diagrams

Distilling infrastructure software into quick and…

Diana Hsieh

Written by

Co-founder @ InPlace Health. Co-founder @ Hone Club. Find me @dianasaur323

Learning with Diagrams

Distilling infrastructure software into quick and understandable diagrams

Diana Hsieh

Written by

Co-founder @ InPlace Health. Co-founder @ Hone Club. Find me @dianasaur323

Learning with Diagrams

Distilling infrastructure software into quick and understandable diagrams

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store