Details
Minor
Description
------------------------
LATEST FOREIGN KEY ERROR
------------------------
InnoDB: Renaming table `mysql`.<result 2 when explaining filename '#sql-71b4_3b'> to `mysql`.`db` failed!
InnoDB: Renaming table `mysql`.<result 2 when explaining filename '#sql-71b4_4b'> to `mysql`.`db` failed!
InnoDB: Renaming table `mysql`.<result 2 when explaining filename '#sql-71b4_4b'> to `mysql`.`host` failed!
InnoDB: Renaming table `mysql`.<result 2 when explaining filename '#sql-71b4_4b'> to `mysql`.`user` failed!
You see these errors if you attempt to convert a MyISAM table in the 'mysql' database to an InnoDB table.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: SHOW INNODB STATUS reports non-FK errors in the FK section
Patch for Maria:
$ bzr diff
=== modified file 'storage/innodb_plugin/handler/ha_innodb.cc'
— storage/innodb_plugin/handler/ha_innodb.cc 2011-06-07 16:13:02 +0000
+++ storage/innodb_plugin/handler/ha_innodb.cc 2011-07-05 06:53:14 +0000
@@ -7174,16 +7174,6 @@
error = row_rename_table_for_mysql(
norm_from, norm_to, trx, lock_and_commit);
- if (error != DB_SUCCESS)
{
- FILE* ef = dict_foreign_err_file;
-
- fputs("InnoDB: Renaming table ", ef);
- ut_print_name(ef, trx, TRUE, norm_from);
- fputs(" to ", ef);
- ut_print_name(ef, trx, TRUE, norm_to);
- fputs(" failed!\n", ef);
- }
-
if (lock_and_commit) {
row_mysql_unlock_data_dictionary(trx);
Re: SHOW INNODB STATUS reports non-FK errors in the FK section
While the fix is trivial, I'd prefer for us to wait until upstream MySQL fixes this bug, as it's pretty minor and is probably not worth the maintenance for us in Percona Server.
Launchpad bug id: 691601
Reproducible on MySQL 5.5.13, but not on the current trees, I presume it's been fixed (although the upstream bug is still open, I added a question about it).
Apparently fixed in (at least) 5.5 and further
Re: SHOW INNODB STATUS reports non-FK errors in the FK section
I know that making those tables InnoDB is not supported. I assume that those types of errors can show up in the FK section under conditions other than the example I provided, if an ALTER TABLE can't complete properly.