Bug #31431 multi table update of innodb and myisam crash

• Submitted: 6 Oct 2007 18:03
• Modified: 6 Oct 2007 18:10
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Duplicate
• Category: MySQL Server: General
• Severity: S3 (Non-critical)
• Version: 5.1.22
• OS: Any
• CPU Architecture: Any

[6 Oct 2007 18:03] Shane Bester

Description:
multi table update caused a debug assertion to fail:

InnoDB: Rolling back of trx id 0 4970 completed
071006 19:57:31  InnoDB: Rollback of non-prepared transactions completed
071006 19:57:31 [Note] mysqld-debug: ready for connections.
Version: '5.1.22-rc-community-debug'  socket: ''  port: 3306  MySQL Community Server - Debug (GPL)
Assertion failed: trans_safe || !updated || thd->transaction.stmt.modified_non_trans_table, file .\sql_update.cc, line 1974

mysqld-debug.exe!_NMSG_WRITE
mysqld-debug.exe!abort
mysqld-debug.exe!_assert
mysqld-debug.exe!multi_update::send_eof
mysqld-debug.exe!do_select
mysqld-debug.exe!JOIN::exec
mysqld-debug.exe!mysql_select
mysqld-debug.exe!mysql_multi_update
mysqld-debug.exe!mysql_execute_command
mysqld-debug.exe!mysql_parse
mysqld-debug.exe!dispatch_command
mysqld-debug.exe!do_command
mysqld-debug.exe!handle_one_connection
mysqld-debug.exe!pthread_start
mysqld-debug.exe!_threadstart
kernel32.dll!FlsSetValue

How to repeat:
I have a testcase, will upload it tonight.

[6 Oct 2007 18:04] MySQL Verification Team

complete stack trace.

Attachment: bug31431_5.1.22_windows_stack.txt (text/plain), 2.44 KiB.

[6 Oct 2007 18:10] MySQL Verification Team

appears to be the same as Bug #30763