diff options
author | Marko Mäkelä <marko.makela@mariadb.com> | 2017-12-18 19:46:23 +0200 |
---|---|---|
committer | Marko Mäkelä <marko.makela@mariadb.com> | 2017-12-18 19:51:44 +0200 |
commit | 40088bfc7e100294d622ab32a6e7cbcb79c12eab (patch) | |
tree | 8a735f0fa20e0e72cce666b6ec22f7b524bae491 /sql/structs.h | |
parent | 03e91ce324465e465468021edd050c3b73d4cee3 (diff) | |
download | mariadb-git-40088bfc7e100294d622ab32a6e7cbcb79c12eab.tar.gz |
MDEV-13407 innodb.drop_table_background failed in buildbot with "Tablespace for table exists"
The InnoDB background DROP TABLE queue is something that we should
really remove, but are unable to until we remove dict_operation_lock
so that DDL and DML operations can be combined in a single transaction.
Because the queue is not persistent, it is not crash-safe. In stable
versions of MariaDB, we can only try harder to drop all enqueued
tables before server shutdown.
row_mysql_drop_t::table_id: Replaces table_name.
row_drop_tables_for_mysql_in_background():
Do not remove the entry from the list as long as the table exists.
In this way, the table should eventually be dropped.
Diffstat (limited to 'sql/structs.h')
0 files changed, 0 insertions, 0 deletions