[MDEV-3615] LP:588599 - ARCHIVE tables aren't discoverable after OPTIMIZE Created: 2010-06-02  Updated: 2012-10-04  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Stewart Smith Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug588599.xml     Text File LPexportBug588599_archive_discover_after_optimize.patch    

 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

 Comments   
Comment by Stewart Smith [ 2010-06-02 ]

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.

Comment by Stewart Smith [ 2010-06-02 ]

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

Comment by Michael Widenius [ 2010-07-20 ]

Re: ARCHIVE tables aren't discoverable after OPTIMIZE
Fixed pushed into 5.2

Comment by Rasmus Johansson (Inactive) [ 2010-08-12 ]

Launchpad bug id: 588599

Generated at Thu Feb 08 06:49:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.