Postgres and the Perils of Abstraction

  1. Read Committed:
    Each read within a transaction will see a consistent view of the database. If, however, a transaction has multiple reads, each of these reads can see different views of the database!
  2. Repeatable Read:
    Each transaction sees a consistent view of the database (this includes all the reads within the transaction)
  3. Serializable:
    Concurrent transactions can only go ahead if the system can prove that if they run in some specific order, they will always have the same result. Or, in other words, it’s as if all the transactions happen one after the other.




That Tall Bald Indian Guy…

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Writing, Accessing, and Modifying Nested APIs with Ruby & Sinatra

Android Matrix Analysis

KEDA Up Close: Kubernetes-based, Event-Driven Autoscaling

Field Report on the Kernel Community Workshop

Creating a Todo App with React, Apollo, and Hasura

Create a database with Heroku

Advanced SQL: An Introduction to Window Function

Requirements of Compliant Data Backup for Cloud Native Applications on AWS

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
Mahesh Paolini-Subramanya

Mahesh Paolini-Subramanya

That Tall Bald Indian Guy…

More from Medium

Intro to GraphQL

How to use the latest Husky 8 with Commitizen for adding git hooks to your projects

An overview of version control and non-relational databases

Getting Started with GraphQL (Part I)