Transactionalism Explained
summary
Explains how database transactions work internally using PostgreSQL as an example, focusing on Write-Ahead Logging (WAL) and MVCC (multi-version concurrency control). Describes how those mechanisms provide atomicity for single transactions and maintain integrity across crashes.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:22Transactions in practice
- 1:03Starting a transaction
- 2:27Transaction atomicity
- 4:14MVCC in PostgreSQL
- 6:21MVCC demo
- 9:05Default isolation level
- 11:11Non-repeatable reads problem
- 11:31Repeatable Read level
- 14:54Transaction durability
related talks
16mTransactionality Explained
41mTransactions: myths, surprises and opportunities
43mBeing Transactional in 2019 — What Does That Actually Mean?
47mBeing transactional in 2019 - what does this 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