Concurrency Control: How It Really Works
Contents |
← Back to MySQL University main page
[edit] Concurrency Control: How It Really Works
- Date and time: September 24, 2009, 14:00 UTC
- To attend, point your browser to this address. Note that the meeting room will open only 15 minutes before the hour. (This line can be removed after the session.)
- Presenter: Heikki Tuuri, Oracle
- Host: Paul DuBois
- Abstract: This presentation describes how InnoDB manages concurrency control, so that the system protects data integrity. We will begin with the basics of transaction management, including a discussion of the ACID (atomicity, consistency, isolation, and durability) properties, and explain various transaction modes, locking, deadlocks, and more advanced topics such as the impact of next-key (gap) locking, referential integrity, XA (distributed transaction management) support and more. While the discussion will focus on the InnoDB implementation, many of the concepts presented apply to other database systems and storage engines.
- Presentation slides: Concurrency control: how it really works
- Session recording: (stream) (download)
- Chat transcript)