Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3.2
-
10.3.3-1
Description
Currently, InnoDB allows instant ADD COLUMN together with DROP INDEX, but not with ADD INDEX, even if the index is to be added on some other column than the instantly added column.
Also, if the table contains SPATIAL or FULLTEXT index, LOCK=NONE is wrongly refused for ADD COLUMN.
Attachments
Issue Links
- causes
-
MDEV-14396 Assertion `(ha_alter_info->handler_flags & ~INNOBASE_INPLACE_IGNORE) == Alter_inplace_info::CHANGE_CREATE_OPTION' failed in create_option_need_rebuild
- Closed
-
MDEV-15828 Server crash or assertion `num_fts_index <= 1' failure upon ALTER TABLE adding two fulltext indexes
- Closed
- relates to
-
MDEV-14219 Allow online table rebuild when encryption or compression parameters change
- Closed
-
MDEV-14246 Skip the ha_innobase::prepare_inplace_alter_table() phase if no inplace_alter_table() phase is needed
- Closed
-
MDEV-28912 Assertion `ha_alter_info->key_count + (dict_table_get_first_index(ctx->new_table))->is_gen_clust() + .... in bool prepare_inplace_alter_table_dict
- Closed
-
MDEV-11369 Instant add column for InnoDB
- Closed
-
MDEV-30969 Some ALGORITHM=INSTANT checks are missing from handler::can_convert_nocopy()
- Open