| Showing all 6 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 26284 | 2007-02-12 12:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6694 days) | S3 | 5.0.bk | Linux (Linux) | Any | bug #26273 / optimize, not executed for index, if datafile is gap-free |
| 86460 | 2017-05-25 14:19 | 2017-06-14 3:38 | MySQL Server: InnoDB storage engine | Verified (3205 days) | S3 | 5.6 5.7 | Any | Any | Deleted DOCID are not maintained during OPTIMIZE of InnoDB FULLTEXT tables |
| 71146 | 2013-12-14 11:34 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (4467 days) | S3 | any | Any | Any | Manual does not explain when REPAIR or OPTIMIZE TABLE uses repair by sorting |
| 119980 | 2026-03-04 11:56 | 2026-03-04 11:56 | MySQL Server: FULLTEXT search | Open | S3 | 8.4.8 | Any | Any | Optimize full text only not working when trying to fix FTS index after tablespace import |
| 80503 | 2016-02-25 5:29 | 2016-02-25 5:42 | MySQL Server: MyISAM storage engine | Verified (3666 days) | S3 | 5.6.29 | Red Hat | Any | optimize MyISAM leads to corrupted index |
| 84081 | 2016-12-06 18:38 | 2021-11-09 15:27 | MySQL Server: Options | Verified (3378 days) | S3 | 5.7.14, 5.7.16 | Ubuntu | Any | super_read_only and read_only not allowing OPTIMIZE TABLE on 5.7 |
| Showing all 6 (Edit, Save, CSV, Feed) |
