# # Bug #29846292 ROLLBACK OF BIG TRANSACTION DUE TO CONFLICT REMAINS IN HUNG STATE # --source include/have_debug.inc --source include/have_innodb_max_16k.inc # Valgrind can hang or return spurious messages on DBUG_SUICIDE --source include/not_valgrind.inc CREATE TABLE t1 (f1 INT PRIMARY KEY, f2 LONGBLOB, KEY(f2(50))) ENGINE=InnoDB; SHOW CREATE TABLE t1; START TRANSACTION; INSERT INTO t1 VALUES (1, REPEAT('abcdefghijklmnopqrstuvwxyz1234', 6006)); SET DEBUG = '+d,crash_middle_of_lob_rollback_6'; --source include/expect_crash.inc --error CR_SERVER_LOST ROLLBACK; --echo # Verify that before the crash, we HAVE NOT reached the index length=4 yet let SEARCH_FILE= $MYSQLTEST_VARDIR/log/mysqld.1.err; let SEARCH_PATTERN= Rolling back LOB for transaction \d+ undo number \d+ : current index length 4\.; --source include/search_pattern.inc --source include/start_mysqld.inc SELECT * FROM t1 FOR UPDATE; DROP TABLE t1; --echo # Verify that after the restart, we HAVE reached the index length=4 --source include/search_pattern.inc