[MDEV-15719] ALTER TABLE…ALGORITHM=INPLACE is unnecessarily refused due to innodb_force_recovery Created: 2018-03-29  Updated: 2018-03-29  Resolved: 2018-03-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0.6, 10.1.0, 10.2.2, 10.3.0
Fix Version/s: 10.2.15, 10.3.6

Type: Bug Priority: Minor
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: online-ddl

Issue Links:
Relates
relates to MDEV-13134 Introduce ALTER TABLE attributes ALGO... Closed

 Description   

The function ha_innobase::check_if_supported_inplace_alter() refuses ALGORITHM=INPLACE operation if innodb_force_recovery has been specified. This is unnecessarily strict; only the values 4,5,6 will effectively corrupt the database and require any writes to be blocked. In MariaDB 10.2 we have the flag high_level_read_only that should be used instead.

Furthermore, the high_level_read_only flag should be set if newraw was specified for the InnoDB system tablespace.

I noticed this during the MDEV-13134 code review.
Generated at Thu Feb 08 08:23:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.