Browse Source
Bug#47343: InnoDB fails to clean-up after lock wait timeout on
Bug#47343: InnoDB fails to clean-up after lock wait timeout on
REORGANIZE PARTITION There were several problems which lead to this this, all related to bad error handling. 1) There was several bugs preventing the ddl-log to be used for cleaning up created files on error. 2) The error handling after the copy partition rows did not close and unlock the tables, resulting in deletion of partitions which were in use, which lead InnoDB to put the partition to drop in a background queue.pull/73/head
7 changed files with 157 additions and 28 deletions
-
44mysql-test/r/partition_innodb.result
-
1mysql-test/t/partition_innodb-master.opt
-
45mysql-test/t/partition_innodb.test
-
62sql/ha_partition.cc
-
2sql/sql_parse.cc
-
8sql/sql_partition.cc
-
23sql/sql_table.cc
@ -0,0 +1 @@ |
|||
--innodb_lock_wait_timeout=1 |
|||
Write
Preview
Loading…
Cancel
Save
Reference in new issue