diff options
author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-01-18 12:39:19 +0200 |
---|---|---|
committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-01-18 12:39:19 +0200 |
commit | 4e75bfcb21469c9efbbc55d2ff3978e11475d40d (patch) | |
tree | d3405fa177415d5cb29daf294a2298e54f9461cd /mysql-test/main/innodb_mysql_sync.test | |
parent | a0d3ead83afe7b678c6e2a3ef3a43d05d0093a20 (diff) | |
download | mariadb-git-4e75bfcb21469c9efbbc55d2ff3978e11475d40d.tar.gz |
MDEV-18152 Assertion 'num_fts_index <= 1' failed
InnoDB does not allow creating multiple FULLTEXT INDEX
in ALGORITHM=INPLACE. This constraint was not being properly
enforced after MariaDB started to support ALGORITHM=INSTANT
and instant ADD COLUMN.
As a side effect of this bug, we again allow ALGORITHM=INPLACE
to rebuild a table when one FULLTEXT INDEX survives.
Also, we are returning a more accurate reason for refusing LOCK=NONE.
innobase_fulltext_exist(): Return the number of fulltext indexes.
ha_innobase::check_if_supported_inplace_alter(): If the table
needs to be rebuilt, refuse the operation if multiple fulltext
indexes would remain.
Diffstat (limited to 'mysql-test/main/innodb_mysql_sync.test')
-rw-r--r-- | mysql-test/main/innodb_mysql_sync.test | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mysql-test/main/innodb_mysql_sync.test b/mysql-test/main/innodb_mysql_sync.test index 66935f811d7..4026080c4b4 100644 --- a/mysql-test/main/innodb_mysql_sync.test +++ b/mysql-test/main/innodb_mysql_sync.test @@ -650,7 +650,7 @@ SET DEBUG_SYNC= 'alter_table_copy_after_lock_upgrade SIGNAL upgraded'; --echo #Setup a table with FULLTEXT index. --connection default -CREATE TABLE t1(fld1 CHAR(10), FULLTEXT(fld1)) ENGINE= INNODB; +CREATE TABLE t1(fld1 CHAR(10), FULLTEXT(fld1), FULLTEXT(fld1)) ENGINE= INNODB; INSERT INTO t1 VALUES("String1"); --echo #OPTIMIZE TABLE operation. |