mariadb/storage
Satya B f6c28cd948 BUG#40827 - Killing insert-select to MyISAM can cause table corruption
Killing insert-select statement on MyISAM corrupts the table.
                  
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.
2009-04-16 17:02:56 +05:30
..
archive fixed archive test. It might be OOM error on boxes with low amount of memory. 2009-03-26 18:27:34 +04:00
blackhole Added "Sun Microsystems, Inc." to copyright headers on files modified 2008-11-10 21:21:49 +01:00
csv compiler warning fix 2009-03-24 13:02:01 +04:00
example
federated Bug#29125 Windows Server X64: so many compiler warnings 2009-02-13 11:41:47 -05:00
heap Bug#29125 Windows Server X64: so many compiler warnings 2009-02-13 11:41:47 -05:00
ibmdb2i merging with mysql-5.1-bugteam 2009-04-13 17:05:40 +05:30
innobase Applying InnoDB snashot 5.1-ss4699, part 3. Fixes BUG#43660 2009-04-15 18:11:54 +05:30
myisam BUG#40827 - Killing insert-select to MyISAM can cause table corruption 2009-04-16 17:02:56 +05:30
myisammrg Bug#37631 Incorrect key file for table after upgrading from 5.0 to 5.1 2009-04-08 12:25:19 +05:30
ndb Merge from 5.0-bugteam 2009-04-16 11:47:21 +02:00
Makefile.am Add the IBM DB2 for i storage engine. 2009-02-15 03:18:30 +01:00