mirror of
https://github.com/MariaDB/server.git
synced 2025-07-30 16:24:05 +03:00
Fix Bug #48026 Log start and end of InnoDB buffer pool initialization
to the error log rb://513 approved by Sunny Bains
This commit is contained in:
@ -1012,12 +1012,13 @@ ha_innobase::prepare_drop_index(
|
||||
index->to_be_dropped = TRUE;
|
||||
}
|
||||
|
||||
/* If FOREIGN_KEY_CHECK = 1 you may not drop an index defined
|
||||
/* If FOREIGN_KEY_CHECKS = 1 you may not drop an index defined
|
||||
for a foreign key constraint because InnoDB requires that both
|
||||
tables contain indexes for the constraint. Note that CREATE
|
||||
INDEX id ON table does a CREATE INDEX and DROP INDEX, and we
|
||||
can ignore here foreign keys because a new index for the
|
||||
foreign key has already been created.
|
||||
tables contain indexes for the constraint. Such index can
|
||||
be dropped only if FOREIGN_KEY_CHECKS is set to 0.
|
||||
Note that CREATE INDEX id ON table does a CREATE INDEX and
|
||||
DROP INDEX, and we can ignore here foreign keys because a
|
||||
new index for the foreign key has already been created.
|
||||
|
||||
We check for the foreign key constraints after marking the
|
||||
candidate indexes for deletion, because when we check for an
|
||||
|
Reference in New Issue
Block a user