Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.5, 10.2(EOL)
Description
Immediately after the push of MDEV-16678 into 10.5, we got the following failure on one platform:
10.5 adb117cf6901a0e0da7577267be1209359892207 |
innodb.foreign_key 'innodb' w1 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2019-12-10 21:04:58
|
line
|
2019-12-10 21:04:53 3 [Warning] InnoDB: MySQL is trying to drop database `best`.`` though there are still open handles to table `best`.`#sql-ib1148`.
|
^ Found warnings in /dev/shm/var/1/log/mysqld.1.err
|
I am unable to repeat the failure. I believe that this could have been caused by the second commit of MDEV-16678.
I believe that this would be best addressed by MDEV-8069 where the to-be-dropped tables would be moved into a separate directory.
Attachments
Issue Links
- is blocked by
-
MDEV-21175 Remove dict_table_t::n_foreign_key_checks_running from InnoDB
- Closed
-
MDEV-21602 CREATE TABLE…PRIMARY KEY…SELECT workaround causes DROP TABLE to ignore locks
- Closed
- is duplicated by
-
MDEV-22955 innodb.innodb-alter fails in buildbot with extra warning
- Closed
- relates to
-
MDEV-16678 Use MDL for innodb background threads instead of dict_operation_lock
- Closed