[MDEV-26966] The parameter innodb_force_load_corrupted makes no sense Created: 2021-11-03  Updated: 2021-11-04  Resolved: 2021-11-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.6.3, 10.6.4, 10.6.5
Fix Version/s: 10.6.6

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: recovery

Issue Links:
Relates
relates to MDEV-11412 Ensure that table is truly dropped wh... Closed
relates to MDEV-17567 Atomic DDL Closed
relates to MDEV-25506 Atomic DDL: .frm file is removed and ... Closed
relates to MDEV-25683 Atomic DDL: With innodb_force_recover... Closed
relates to MDEV-26933 InnoDB fails to detect page number mi... Closed

 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.

 Comments   
Comment by Marko Mäkelä [ 2021-11-04 ]

The read-only parameter innodb_force_load_corrupted will be marked as removed starting with the 10.6.6 release.

This will also remove some redundant messages that caught my eye in MDEV-25683.

Generated at Thu Feb 08 09:49:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.