Bug #60613 | SYS_TABLES is accessed before recv_recovery_from_checkpoint_finish() may crash | ||
---|---|---|---|
Submitted: | 24 Mar 2011 3:29 | Modified: | 16 Jan 2013 19:53 |
Reporter: | Yasufumi Kinoshita | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.0, 5.1.56, 5.1.67 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[24 Mar 2011 3:29]
Yasufumi Kinoshita
[11 Jan 2012 15:50]
Valeriy Kravchuk
See bug #59910 also.
[13 Mar 2012 19:43]
Sveta Smirnova
Yasufumi, bug #59910 with similar symptom during MEB restore is not repeatable now. Is it fixed in latest InnoDB code?
[14 Mar 2012 0:15]
Yasufumi Kinoshita
Sveta, mysql-5.1/storage/innobase/srv/srv0start.c has the code still. -------- TODO: We may have incomplete transactions in the data dictionary tables. Does that harm the scanning of the data dictionary below? */ dict_check_tablespaces_and_store_max_id( recv_needed_recovery); } ..... recv_recovery_from_checkpoint_finish(); ---------- Does MEB use the built-in InnoDB's recovery code?
[22 Mar 2012 19:37]
Sveta Smirnova
Yasufumi, yes, it does. But it lately started to use 5.5, so probably this is the reason for fix of second bug.
[16 Jan 2013 19:53]
Sveta Smirnova
I think this should be verified finally: code still exists in 5.1 and solution of MEB bug can prove this could lead to crash.