Bug #118560 drop full text can not instant

• Submitted: 30 Jun 2025 11:58
• Modified: 30 Jun 2025 13:01
• Reporter: zongyi chen (OCA)
• Status: Verified
• Category: MySQL Server: DDL
• Severity: S3 (Non-critical)
• Version: 8.0, 8.4
• OS: Any
• CPU Architecture: Any

[30 Jun 2025 11:58] zongyi chen

Description:
The table with full-text indexing reports an instant DDL error, so after deleting the full-text index, it still reports an error.

How to repeat:
mysql> CREATE TABLE t (content longtext, FULLTEXT KEY idx_content (content));
Query OK, 0 rows affected (0.48 sec)

mysql> alter table t add a int, algorithm = instant;
ERROR 1846 (0A000): ALGORITHM=INSTANT is not supported. Reason: InnoDB presently supports one FULLTEXT index creation at a time. Try ALGORITHM=COPY/INPLACE.

mysql> alter table t drop index idx_content, algorithm = inplace;
Query OK, 0 rows affected (0.17 sec)
Records: 0  Duplicates: 0  Warnings: 0

mysql> alter table t add a int, algorithm = instant;
ERROR 1845 (0A000): ALGORITHM=INSTANT is not supported for this operation. Try ALGORITHM=COPY/INPLACE.

mysql> optimize table t;
+--------+----------+----------+-------------------------------------------------------------------+
| Table  | Op       | Msg_type | Msg_text                                                          |
+--------+----------+----------+-------------------------------------------------------------------+
| test.t | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| test.t | optimize | status   | OK                                                                |
+--------+----------+----------+-------------------------------------------------------------------+
2 rows in set (0.21 sec)

mysql> alter table t add a int, algorithm = instant;
Query OK, 0 rows affected (0.07 sec)
Records: 0  Duplicates: 0  Warnings: 0

[30 Jun 2025 13:01] MySQL Verification Team

Hello zongyi chen,

Thank you for the report and test case.
Verified as described.

regards,
Umesh

[30 Jun 2025 13:01] MySQL Verification Team

Related - Bug #104899

[17 Apr 12:01] Dyre Tjeldvoll

Posted by developer:
 
Thank you for the bug report. I am not sure if this is a bug or desired behaviour, but I have 
changed the category to Innodb so that they can evaluate it.