This session is about how 5.5 is different. Like a car equipped with an ABS, MySQL 5.5, behaving almost the same from external point of view, is able to deal gracefully with a large quantity of replication failures, deadlocks, and ACID violation issues that 5.1 and earlier users simply had to live with.
It can be of interest to engine writers, which should be aware of the new subsystem and its implications on the storage engine API (including the engine’s ability to plug into the new deadlock detector, making cross-storage-engine deadlock resolution possible), as well as MySQL field experts, who may want to understand how the new server operates in some of its most critical parts.
If Drizzle team has interest, the session could be turned into a panel discussion, to give people a clearer idea how different forks approach the same problem (Drizzle, which doesn’t have stored procedures or triggers, adopted a different solution).
Konstantin Osipov has been a software engineer and engineering lead at MySQL since 2003. His main areas in the server are locking, parsing, execution of prepared statements and stored procedures. He was the implementer of support for Dynamic SQL in 5.0. In his other life Konstantin is a Moscow dweller with a not
uncommon combination of such hobbies as yoga, running, and computers.
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at firstname.lastname@example.org
For media partnerships, contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at email@example.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference Bulletin (login required).
View a complete list of O'Reilly MySQL Conference Contacts