Bug #85090 Assert in DA for Sql_cmd_update::update_single_table
Submitted: 21 Feb 2017 5:53 Modified: 13 Apr 2017 16:44
Reporter: Shipra Jain Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:8.0.1 OS:Any
Assigned to: CPU Architecture:Any

[21 Feb 2017 5:53] Shipra Jain 
Description:
Assert in DA for Sql_cmd_update::update_single_table

commit a0ac92b3907d59bd62455c5f749ab0975f8b6d76
Merge: da89e4e c2b35de
Author: Anushree Prakash B <anushree.prakash.b@oracle.com>
Date:   Fri Feb 10 11:58:49 2017 +0530

# 2017-02-20T15:09:59 #4  0x00007f848ea1e8a5 in raise () from /lib64/libc.so.6
# 2017-02-20T15:09:59 #5  0x00007f848ea20085 in abort () from /lib64/libc.so.6
# 2017-02-20T15:09:59 #6  0x00007f848ea17a1e in __assert_fail_base () from /lib64/libc.so.6
# 2017-02-20T15:09:59 #7  0x00007f848ea17ae0 in __assert_fail () from /lib64/libc.so.6
# 2017-02-20T15:09:59 #8  0x0000000001969f00 in Diagnostics_area::set_ok_status (this=0x7f84040038a8, affected_rows=0, last_insert_id=0, message_text=0x7f8480225e10 "Rows matched: 0  Changed: 0  Warnings: 3") at /log/RQG/shipjain/trunk/sql/sql_error.cc:406
# 2017-02-20T15:09:59 #9  0x0000000001961fb2 in my_ok (thd=0x7f8404000be0, affected_rows=0, id=0, message=0x7f8480225e10 "Rows matched: 0  Changed: 0  Warnings: 3") at /log/RQG/shipjain/trunk/sql/sql_class.h:4104
# 2017-02-20T15:09:59 #10 0x0000000001fc7691 in Sql_cmd_update::update_single_table (this=0x7f8404bf55b8, thd=0x7f8404000be0) at /log/RQG/shipjain/trunk/sql/sql_update.cc:1074
# 2017-02-20T15:09:59 #11 0x0000000001fc8f9c in Sql_cmd_update::execute_inner (this=0x7f8404bf55b8, thd=0x7f8404000be0) at /log/RQG/shipjain/trunk/sql/sql_update.cc:1559
# 2017-02-20T15:09:59 #12 0x0000000001a0b2f5 in Sql_cmd_dml::execute (this=0x7f8404bf55b8, thd=0x7f8404000be0) at /log/RQG/shipjain/trunk/sql/sql_select.cc:628
# 2017-02-20T15:09:59 #13 0x00000000019b94f3 in mysql_execute_command (thd=0x7f8404000be0, first_level=true) at /log/RQG/shipjain/trunk/sql/sql_parse.cc:3260
# 2017-02-20T15:09:59 #14 0x00000000019be9e2 in mysql_parse (thd=0x7f8404000be0, parser_state=0x7f8480227540) at /log/RQG/shipjain/trunk/sql/sql_parse.cc:5200
# 2017-02-20T15:09:59 #15 0x00000000019b5366 in dispatch_command (thd=0x7f8404000be0, com_data=0x7f8480227d40, command=COM_QUERY) at /log/RQG/shipjain/trunk/sql/sql_parse.cc:1535
# 2017-02-20T15:09:59 #16 0x00000000019b41ee in do_command (thd=0x7f8404000be0) at /log/RQG/shipjain/trunk/sql/sql_parse.cc:1122
# 2017-02-20T15:09:59 #17 0x0000000001c99365 in handle_connection (arg=0x7824ed0) at /log/RQG/shipjain/trunk/sql/conn_handler/connection_handler_per_thread.cc:323
# 2017-02-20T15:09:59 #18 0x000000000295d5d2 in pfs_spawn_thread (arg=0x780b660) at /log/RQG/shipjain/trunk/storage/perfschema/pfs.cc:2390
# 2017-02-20T15:09:59 #19 0x00007f848fd69851 in start_thread () from /lib64/libpthread.so.0
# 2017-02-20T15:09:59 #20 0x00007f848ead367d in clone () from /lib64/libc.so.6

How to repeat:
RQG to repro
==============
perl runtest.pl --queries=100000000 –seed=24802 --threads=1 --duration=2400 --querytimeout=60 --reporter=Shutdown,Backtrace,QueryTimeout,ErrorLog,ErrorLogAlarm --mysqld=--log-output=table --mysqld=--sql_mode=STRICT_ALL_TABLES,NO_ZERO_DATE,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO --sqltrace --notnull --basedir=/log/RQG/shipjain/trunk --grammar=/log/RQG/shipjain/mysql-meta-sync-vigdis29/internal/rqg_grammars/temporal/temporal_replication.yy --mtr-build-thread=121 –vardir=/log/RQG/shipjain/rqg/debug

MTR test to Repro attached
[28 Feb 2017 8:59] Shipra Jain 
Posted by developer:
 
I could repro the issue on trunk with following latest commit commit a0ac92b3907d59bd62455c5f749ab0975f8b6d76 (10th Feb 2017). Removing the mysql-trunk-meta-sync branch tag.
[13 Apr 2017 16:44] Paul DuBois 
Posted by developer:
 
Noted in 8.0.2 changelog.

In strict SQL mode, an ER_TRUNCATED_WRONG_VALUE error could be
converted from a warning to an error but then ignored, leading to a
raised assertion.