Commit 64b697ca authored by Aditya A's avatar Aditya A

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 ]
parent e8232b1d
...@@ -7652,16 +7652,6 @@ innobase_rename_table( ...@@ -7652,16 +7652,6 @@ innobase_rename_table(
error = row_rename_table_for_mysql( error = row_rename_table_for_mysql(
norm_from, norm_to, trx, lock_and_commit); 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) { if (lock_and_commit) {
row_mysql_unlock_data_dictionary(trx); row_mysql_unlock_data_dictionary(trx);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment