Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
Description
A table is allowed to be dropped despite being in use:
|
--connection crash_me
|
CREATE TABLE t1 (pk INT PRIMARY KEY) ENGINE=InnoDB; |
xa start '1'; insert into t1 set pk=1; xa end '1'; xa prepare '1'; |
|
# KILL server_process & restart
|
xa recover; # =>
|
+----------+--------------+--------------+------+ |
| formatID | gtrid_length | bqual_length | data |
|
+----------+--------------+--------------+------+ |
| 1 | 1 | 0 | 1 |
|
+----------+--------------+--------------+------+ |
1 row in set (0.00 sec) |
|
--connection default
|
--error 0
|
DROP TABLE t1; |
Notice that use cases of survived prepared user XA have involved MDEV-742 disconnected prepared so instead of the crash a simple --diconnect would leave the trx prepared and offended by the following DROP.
Attachments
Issue Links
- blocks
-
MDEV-21175 Remove dict_table_t::n_foreign_key_checks_running from InnoDB
- Closed
-
MDEV-21283 InnoDB: MySQL is trying to drop database…open handles to table …`#sql-ib1148`
- Closed
-
MDEV-22733 XA PREPARE breaks MDL in pseudo_slave_mode=1
- Stalled
- is part of
-
MDEV-25506 Atomic DDL: .frm file is removed and orphan InnoDB tablespace is left behind upon crash recovery
- Closed
- relates to
-
MDEV-742 LP:803649 - Xa recovery failed on client disconnection
- Closed
-
MDEV-23223 If you cancel CTAS Query on MariaDB Server, it will not be canceled and Rollback will be executed
- Closed
-
MDEV-23484 Rollback unnecessarily acquires dict_operation_lock for every row
- Closed
-
MDEV-25921 Implement CREATE TABLE...SELECT in one transaction
- Open
-
MDEV-21820 create table ... select is metadata locking information_schema
- Closed
-
MDEV-23234 move MDL from THD to st_transaction
- Open
-
MDEV-24225 Long semaphore wait in dict0dict.cc line 943 and semaphore wait >600 sec kill
- Closed