diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-02-15 13:56:04 +0200 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-02-15 13:56:04 +0200 |
| commit | e1af460146eda298ea403ec01f854aa4babea250 (patch) | |
| tree | 00aa2cc5aa55d1852663d30a5489be804c96b554 /libmysqld | |
| parent | 2b921845ac5ba54da607e781e63d345be83b98b1 (diff) | |
| download | mariadb-git-e1af460146eda298ea403ec01f854aa4babea250.tar.gz | |
MDEV-18579 Assertion !ctx->online || num_fts_index == 0
instant_alter_column_possible(): Add the other MDEV-17459 work-around
condition. The existence of fulltext indexes only prevents instant
DROP COLUMN or changing the order of columns. Other forms of instant
ALTER TABLE are no problem.
Before commit 4e7ee166a9c76eb3546356aabfd2dbc759671cd0 that merged
the MDEV-18295 fix from 10.3, the work-around of MDEV-17459 in
instant_alter_column_possible() was categorically refusing any
ALGORITHM=INSTANT if any FULLTEXT INDEX was present. After that commit,
a related condition was only present in prepare_inplace_alter_table_dict()
but not in the other callers of instant_alter_column_possible().
Diffstat (limited to 'libmysqld')
0 files changed, 0 insertions, 0 deletions