InnoDB provides a reliable, true-and-tested automatic crash recovery for MySQL database users. It is based on a redo log and write-ahead logging, two techniques that are used in most of the leading database engines in the world. We will explain these techniques in depth, and present some benchmarks of the crash recovery time.
InnoDB’s media recovery is done from a (hot) backup of a database, using the MySQL binlog to replay the transactions just as they happened originally. We will explain the difference between MySQL’s statement-based and row-based replication and binlogging, and how they should be used to ensure a successful replay of transactions.
Heikki Tuuri is the creator of the InnoDB transactional storage engine in MySQL. He founded Innobase Oy in 1995 and is the CEO of the company. Prior to founding Innobase Oy, Tuuri worked at the University of Helsinki, from which he also received a Ph.D, degree in mathematical logic in 1990.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at email@example.com
Download the MySQL Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the MySQL Conference newsletter.
View a complete list of MySQL contacts.