Back to Browse

Transaction Isolation Levels With PostgreSQL as an example

38.6K views
Nov 8, 2020
8:17

In this video, Boris Strelnikov will explain which transaction isolation levels exist in databases and what you should be aware of as a developer. You will see dirty read, lost update, non-repeatable read, phantoms and serialization anomaly - most of them demoed inside PostgreSQL database. You can hire Boris as your programming mentor or get a consultation from him here: https://mkdev.me/en/mentors/risentveber Check out mkdev dispatch, bi-weekly newsletter about DevOps and Cloud Native - https://mkdev.me/dispatch DevOps Accents is our monthly podcast, where 3 mkdev founders chat about DevOps, Cloud and Life: https://mkdev.me/podcast At mkdev we provide all range of IT services, from trainings and workshops to audit and consulting. Check out our website: https://mkdev.me/en/b or contact us at [email protected] #databases #rdbms #postgresql #transactionisolation #acid

Download

1 formats

Video Formats

360pmp49.1 MB

Right-click 'Download' and select 'Save Link As' if the file opens in a new tab.

Transaction Isolation Levels With PostgreSQL as an example | NatokHD