ARCHIVE tables aren't discoverable after OPTIMIZE
Bug #588599 reported by
Stewart Smith
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MariaDB |
Fix Released
|
Medium
|
Michael Widenius | ||
| MySQL Server |
Unknown
|
Unknown
|
|||
Bug 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
Revision history for this message
| Stewart Smith (stewart) wrote | #1 |
| Changed in maria: | |
| importance: | Undecided → Medium |
| Changed in maria: | |
| assignee: | nobody → Michael Widenius (monty) |
Revision history for this message
| Michael Widenius (monty) wrote | #2 |
| Changed in maria: | |
| status: | New → Fix Committed |
| Changed in maria: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.