Comment 7 for bug 1281810

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote : Re: Loss of records with LOAD INTO using trx split in 5.6

With 5.6 debug build, hit this crash:

2014-02-19 16:57:06 7fe2047f8700 InnoDB: Assertion failure in thread 140608714802944 in file row0mysql.cc line 3249
InnoDB: Failing assertion: (trx)->start_file == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

with

MySQL [test4]> SELECT * FROM tbtest1 LIMIT 10004 INTO OUTFILE '/tmp/t2';
Query OK, 10004 rows affected (0.15 sec)

MySQL [test4]> truncate tbtest1;
Query OK, 0 rows affected (0.27 sec)

MySQL [test4]> load data infile '/tmp/t2' into table tbtest1;
Query OK, 10004 rows affected (2.51 sec)
Records: 10004 Deleted: 0 Skipped: 0 Warnings: 0

MySQL [test4]> select count(*) from tbtest1;
+----------+
| count(*) |
+----------+
| 10004 |
+----------+
1 row in set (0.04 sec)

MySQL [test4]> truncate tbtest1;
ERROR 2013 (HY000): Lost connection to MySQL server during query