Comment 4 for bug 1217002

Revision history for this message
Hartmut Holzgraefe (hartmut-php) wrote : Re: RENAME/DROP crashes 5.5.30+ with innodb_track_changed_pages

Yes, wording wasn't too clear in the original report, should have been "XtraDB assertion", not "InnoDB assertion" near the top, and "bug introduced by" should have been "problem caused by change made by" ...

On the Innobase/MySQL/Oracle side the code was written, and finally changed, under the assumption that it will only ever be executed single threaded during recovery operations (either on startup within the server itself, or when preparing an ibbackup for restore), so that no dictionary changes could possibly ever happen in parallel to the log reading ...

That's why I only reported the problem here, and not on bugs.mysql.com (although yes, some of the function names and comments were already confusing to begin with, and the "File ops are parsed, but not applied in this function." part now being outright wrong in the case of MLOG_FILE_RENAME