Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
Description:
OPTIMIZE TABLE on an ARCHIVE table rewrites the ARZ file.
It does not copy the FRM stored in the ARZ across. So an ARCHIVE table that has been
OPTIMIZEd cannot be discovered.
How to repeat:
CREATE TABLE t1 (a int) ENGINE=ARCHIVE;
OPTIMIZE TABLE t1;
rm t1.frm
select * from t1;
You can also verify with archive_reader
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: ARCHIVE tables aren't discoverable after OPTIMIZE
I wrote this patch ages ago for MySQL, so no idea if it still applies (it should though, I don't think anybody has touched that bit of ARCHIVE in years).
For whatever reason, nobody gives a damn about the MySQL bug.
Feel free to be responsive and actually apply the patch.
Re: ARCHIVE tables aren't discoverable after OPTIMIZE
Fixed pushed into 5.2
Launchpad bug id: 588599
I wrote this patch ages ago for MySQL, so no idea if it still applies (it should though, I don't think anybody has touched that bit of ARCHIVE in years).
For whatever reason, nobody gives a damn about the MySQL bug.
Feel free to be responsive and actually apply the patch.
My July 2009 patch for MySQL
LPexportBug588599_archive_discover_after_optimize.patch