In this blog series, I’m describing how InnoDB locks
data (tables and rows) in order to provide illusion to clients
that their queries are executed one after another, and how this
was improved in recent releases.
In InnoDB Data Locking – Part 1 “Introduction”
I’ve introduced basic concepts required to understand current
post:
- databases, tables, rows (like files on a shared drive, spreadsheets inside a file, and rows inside a spreadsheet)
- serializability of transactions (ability to explain states observed over time with a convincing story about relative order of parallel operations)
- timeouts (for misbehaving lock owners, and to resolve deadlocks)
- reader-writer lock …