Bug#12762390 SHOW INNODB STATUS REPORTS NON-FK

ERRORS IN THE FK SECTION

ANALYSIS
--------

Any error during the renaming of the table was 
incorrectly logged in the dict_foreign_err_file
and it showed up in foreign key section when
we give the query "show engine innodb status".

FIX
---
Prevent renaming error from being logged in 
dict_foreign_err_file section.  

[Aprooved by marko #rb 2501 ]
This commit is contained in:
Aditya A 2013-12-29 16:55:24 +05:30
parent e8232b1d95
commit 64b697ca99

View file

@ -7652,16 +7652,6 @@ innobase_rename_table(
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);