Comment 11 for bug 1415191

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

That is from history:

origin/mysql-server - [5.6] » git show --pretty=full 901ce53
commit 901ce5314b6b0d4115b0237491e2afaafe5a274e
Author: Thiru <email address hidden>
Commit: Thiru <email address hidden>

    Bug #20144839 AFTER UPDATING TO MYSQL 5.6.22 SERVER
                CRASHES ON EVERY START ATTEMPT

    Description:
    ------------
    push_warning_printf function is used to print the warning message
    to the client. So this function should not invoke while recovering
    the server. Moreover current_thd is NULL while starting the server.

    Solution:
    ---------
     - Avoiding the warning to be printed while recovery.
    This patch already pushed in mysql-5.6.

diff --git a/storage/innobase/handler/ha_innodb.cc b/storage/innobase/handler/ha_innodb.cc
index fab832d..676a20f 100644
--- a/storage/innobase/handler/ha_innodb.cc
+++ b/storage/innobase/handler/ha_innodb.cc
@@ -12102,6 +12102,10 @@ ib_warn_row_too_big(const dict_table_t* table)

        THD* thd = current_thd;

+ if (thd == NULL) {
+ return;
+ }
+
        push_warning_printf(
                thd, MYSQL_ERROR::WARN_LEVEL_WARN, HA_ERR_TO_BIG_ROW,
                "Row size too large (> %lu). Changing some columns to TEXT"
origin/mysql-server - [5.6] » git show --pretty=full 7b17ebb
commit 7b17ebbd86fc9459d14e93760b1d45e327615cc9
Merge: 4423b9b 901ce53
Author: Thiru <email address hidden>
Commit: Thiru <email address hidden>

    Bug #20144839 AFTER UPDATING TO MYSQL 5.6.22 SERVER
                CRASHES ON EVERY START ATTEMPT

        NULL merge from mysql-5.5 to mysql-5.6

Comment states that patch is already pushed to 5.6, but it is not the case...