-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.1.0, 10.2.0, 10.3.0
-
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
-
Labels:
When MariaDB 10.1.0 introduced table options for encryption and compression, it unnecessarily changed ha_innobase::check_if_supported_inplace_alter() so that ALGORITHM=COPY is forced when these parameters differ.
A better solution would be to move the check to innobase_need_rebuild(). In that way, the ALGORITHM=INPLACE interface (yes, the syntax is very misleading) can be used for rebuilding the table much more efficiently, with merge sort, with no undo logging, and allowing concurrent DML operations.
- causes
-
MDEV-15116 Wrong error code/message 1478: 'Table storage engine 'InnoDB' does not support the create option 'ENCRYPTION_KEY_ID'
-
- Open
-
- is duplicated by
-
MDEV-13639 Server crashes in prepare_inplace_alter_table_dict upon altering a table with discarded tablespace
-
- Closed
-
- relates to
-
MDEV-14016 Allow instant ADD COLUMN, ADD INDEX, LOCK=NONE
-
- Closed
-