Bug #27382 OPTIMIZE TABLE seems to apply to the ARCHIVE storage engine
Submitted: 22 Mar 2007 19:01 Modified: 23 Mar 2007 9:59
Reporter: Baron Schwartz (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:all OS:Any (all)
Assigned to: Stefan Hinz CPU Architecture:Any
Tags: archive, Optimize

[22 Mar 2007 19:01] Baron Schwartz
According to http://dev.mysql.com/doc/refman/5.1/en/optimize-table.html,

"OPTIMIZE TABLE works only for MyISAM and InnoDB tables. It does not work for tables created using any other storage engine, including NDB Disk Data tables."

But http://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html says

"You can use OPTIMIZE TABLE to analyze the table and pack it into a smaller format"

How to repeat:

Suggested fix:
It should probably have a note like similar to http://dev.mysql.com/doc/refman/5.0/en/check-table.html, which says

"CHECK TABLE checks a table or tables for errors. CHECK TABLE works for MyISAM, InnoDB, and (as of MySQL 5.0.16) ARCHIVE tables"
[22 Mar 2007 20:09] MySQL Verification Team
Thank you for the bug report.
[23 Mar 2007 9:59] Stefan Hinz
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.