summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAditya A <aditya.a@oracle.com>2013-12-29 16:55:24 +0530
committerAditya A <aditya.a@oracle.com>2013-12-29 16:55:24 +0530
commit64b697ca999d678692ca8db93ed7e42761cc56d6 (patch)
treeb81982a94f3b9c4b938af7af985fcbcc8f30c644
parente8232b1d95aa4806be54c519ea2dbb2fd03fd8a2 (diff)
downloadmariadb-git-64b697ca999d678692ca8db93ed7e42761cc56d6.tar.gz
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 ]
-rw-r--r--storage/innobase/handler/ha_innodb.cc10
1 files changed, 0 insertions, 10 deletions
diff --git a/storage/innobase/handler/ha_innodb.cc b/storage/innobase/handler/ha_innodb.cc
index 546b0b8905b..5652bca5db7 100644
--- a/storage/innobase/handler/ha_innodb.cc
+++ b/storage/innobase/handler/ha_innodb.cc
@@ -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);