Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.6.3, 10.6.4, 10.6.5
Description
MySQL 5.5 introduced a configuration parameter innodb_force_load_corrupted whose purpose was to allow a corrupted table to be dropped.
Given that MDEV-11412 in MariaDB 10.5.4 aims to allow any metadata for a missing or corrupted table to be dropped, and given that MDEV-17567 and MDEV-25506 and related tasks made DDL operations crash-safe, the parameter does not make any sense.
A change that would deprecate and ignore this read-only parameter has been tested by mleich, and no problems related to that were found.
Because this obscure parameter was read-only (not settable by a client), it seems that we could simply declare it with MARIADB_REMOVED_OPTION without breaking anything.
Attachments
Issue Links
- relates to
-
MDEV-11412 Ensure that table is truly dropped when using DROP TABLE
- Closed
-
MDEV-17567 Atomic DDL
- Closed
-
MDEV-25506 Atomic DDL: .frm file is removed and orphan InnoDB tablespace is left behind upon crash recovery
- Closed
-
MDEV-25683 Atomic DDL: With innodb_force_recovery=3 InnoDB: Trying to load index but the index tree has been freed
- Closed
-
MDEV-26933 InnoDB fails to detect page number mismatch
- Closed