Re: REPAIR/CHECK/BACKUP/RESTORE TABLE handling of compressed tables leads to data loss.

Giuseppe Maxia writes:
> HI,
> I've found a problem related to the handling of compressed tables.
> Several MySQL commands (or external tools) don't handle these table
> correctly. Sometimes, this mishandling leads to data loss. 
> 
> In practical terms, this also means that a compressed table with a
> damaged or missing index file (due to other causes) can't be recovered.
> 
> Any fixes / workarounds available?
> 
> Thanks
> 
> Best regards
> 
> Giuseppe Maxia
> 
> P.S. 
> Detailed bug report attached below.
> I've tested this behaviour with two distributions:
> 4.0.16 (Debian out-of-the-box)
> 4.0.18 (binaries compiled by MySQL AB)

Hi!

Thanks for writting to us.

Short answers to your questions.

1) Any write operation on compressed table is not permitted and will
   result in damaged table. This is documented in a manual.

2) Not checking for compressed table, like with BACKUP / RESTORE is a
   bug. We shall enteri it into our bugs system

3) myisamchk can not operate at all without index file. Documented
   behaviour as per our manual. 

-- 

Sincerely,

-- 
For technical support contracts, go to https://order.mysql.com/?ref=msmi
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Mr. Sinisa Milivojevic <[email protected]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB
/_/  /_/\_, /___/\___\_\___/   Full time Developer and Support Coordinator
       <___/   www.mysql.com   Larnaca, Cyprus



-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]