Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Description
In the ALGORITHM=INPLACE API, if the operation involves data changes, such as adding an index or rebuilding the table, it will be necessary to invoke a "prepare" phase followed by a data transformation phase.
Currently, the "prepare" phase is unnecessarily being executed for instant ADD COLUMN (MDEV-11369) and possibly other operations. This causes an unnecessary step to acquire and downgrade an exclusive meta-data lock, before upgrading the lock to exclusive again for executing ha_innobase::commit_inplace_alter_table().
Attachments
Issue Links
- duplicates
-
MDEV-13134 Introduce ALTER TABLE attributes ALGORITHM=NOCOPY and ALGORITHM=INSTANT
- Closed
- relates to
-
MDEV-11369 Instant add column for InnoDB
- Closed
-
MDEV-13134 Introduce ALTER TABLE attributes ALGORITHM=NOCOPY and ALGORITHM=INSTANT
- Closed
-
MDEV-14016 Allow instant ADD COLUMN, ADD INDEX, LOCK=NONE
- Closed