SHOW INNODB STATUS reports non-FK errors in the FK section

Bug #691601 reported by Swany
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MariaDB
New
Undecided
Unassigned
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Undecided
Unassigned
5.1
Won't Fix
Undecided
Unassigned
5.5
Fix Released
Undecided
Unassigned
5.6
Fix Released
Undecided
Unassigned

Bug 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.

Related branches

Revision history for this message
Swany (greenlion) wrote :

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.

Revision history for this message
Stewart Smith (stewart) wrote :

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);

Revision history for this message
Stewart Smith (stewart) wrote :

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.

Changed in percona-server:
status: New → Won't Fix
tags: added: upstream
tags: added: innodb
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2582

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.