Transactionality Explained
summary
Explains how database transactions guarantee data integrity by making multiple operations atomic, using PostgreSQL as the example. Covers PostgreSQL internals: Write-Ahead Logging (WAL) and Multi-Version Concurrency Control (MVCC), and how they ensure atomicity both for normal operations and across crashes.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:23Banking use case
- 1:05BEGIN and COMMIT
- 2:08Atomicity with ROLLBACK
- 3:11PostgreSQL storage and MVCC
- 5:15MVCC example
- 7:41PostgreSQL atomicity
- 8:02PostgreSQL isolation levels
- 9:23Non-repeatable reads
- 10:25Repeatable Read solution
- 12:08Snapshots in Repeatable Read
- 12:49Update conflicts in RR
- 14:14Durability with WAL
- 15:16Conclusion
related talks
17mTransactionalism Explained
47mBeing transactional in 2019 - what does this actually mean?
41mTransactions: myths, surprises and opportunities
43mBeing Transactional in 2019 — What Does That Actually Mean?
45mTransactions and Concurrency Control Patterns
28mUnderstanding Transaction Isolation for App Developers
52mThe Long Transaction — When Size Matters
41mConcurrency, Scalability and Transactions -- Myths and Surprises