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.
upstream fix:
commit 901ce5314b6b0d4 115b0237491e2af aafe5a274e
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: warning_ printf function is used to print the warning message
------------
push_
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 innobase/ handler/ ha_innodb. cc innobase/ handler/ ha_innodb. cc row_too_ big(const dict_table_t* table)
index fab832d..676a20f 100644
--- a/storage/
+++ b/storage/
@@ -12102,6 +12102,10 @@ ib_warn_
THD* thd = current_thd;
+ if (thd == NULL) {
push_warning_ printf(
thd, MYSQL_ERROR: :WARN_LEVEL_ WARN, HA_ERR_TO_BIG_ROW,
"Row size too large (> %lu). Changing some columns to TEXT"
+ return;
+ }
+