Bug #43687 mysql kill transaction
Submitted: 17 Mar 2009 3:53 Modified: 17 Mar 2009 6:12
Reporter: jabincn jabincn Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.30 OS:Any
Assigned to: CPU Architecture:Any

[17 Mar 2009 3:53] jabincn jabincn
Description:
mysql> select count(1) from t_baidu_keyword;
+----------+
| count(1) |
+----------+
|  1000000 | 
+----------+
1 row in set (0.00 sec)

mysql> detete from t_baidu_keyword;

ctrl+c   or  'kill mysqld'

mysql> select count(1) from t_baidu_keyword;
+----------+
| count(1) |
+----------+
|   259889 | 
+----------+
1 row in set (0.00 sec)

How to repeat:
mysql> select count(1) from t_baidu_keyword;
+----------+
| count(1) |
+----------+
|  1000000 | 
+----------+
1 row in set (0.00 sec)

mysql> detete from t_baidu_keyword;

ctrl+c   or  'kill mysqld'

mysql> select count(1) from t_baidu_keyword;
+----------+
| count(1) |
+----------+
|   259889 | 
+----------+
1 row in set (0.00 sec)
[17 Mar 2009 6:12] Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Then you kill mysqld or query you stop query execution in the middle of the operation. So it is expected what it is partially completed.
[3 Jun 2009 20:59] Sveta Smirnova
When I said this is not a bug I assumed you use default not transactional MyISAM storage engine. In case of InnoDB this is bug.
[3 Jun 2009 21:00] Sveta Smirnova
InnoDB bug reported separately: bug #45309