diff options
| author | Satya B <satya.bn@sun.com> | 2009-04-30 12:40:12 +0530 |
|---|---|---|
| committer | Satya B <satya.bn@sun.com> | 2009-04-30 12:40:12 +0530 |
| commit | a5badbfe6d704d70c528c5aeb028e61fa8337c4c (patch) | |
| tree | 7dcdc853e3d1f9a85609d98807f180ca27300e8a /mysql-test/t/myisam_debug.test | |
| parent | 4ba05b50a2df5bb94e8b3ca27323b35624c527c4 (diff) | |
| parent | 24146bb2ab35079262ba8c4b779e09aebe8d1e2a (diff) | |
| download | mariadb-git-a5badbfe6d704d70c528c5aeb028e61fa8337c4c.tar.gz | |
Fix for BUG#40827 - Killing insert-select to MyISAM can cause table corruption
Killing the insert-select statement corrupts the MyISAM table only
when the destination table is empty and when it has indexes. When
we bulk insert huge data and if the destination table is empty we
disable the indexes for fast inserts, data is then inserted and
indexes are re-enabled after bulk_insert operation
Killing the query, aborts the repair table operation during enable
indexes phase leading to table corruption.
We now truncate the table when we detect that enable indexes is
killed for bulk insert query.As we have an empty table before the
operation, we can fix by truncating the table.
mysql-test/r/myisam.result:
Result file for BUG#40827
mysql-test/t/myisam.test:
Testcase for BUG#40827
storage/myisam/ha_myisam.cc:
Fixed end_bulk_insert() method to truncate the table when we detect enable
index operation is killed.
Diffstat (limited to 'mysql-test/t/myisam_debug.test')
0 files changed, 0 insertions, 0 deletions