List:General Discussion« Previous MessageNext Message »
From:Ware Adams Date:September 27 2004 4:55pm
Subject:Re: mysqldump --opt crashes server on InnoDB tables
View as plain text  
On Sep 27, 2004, at 12:09 PM, Thomas Plümpe wrote:

>>> So I eventually installed a MySQL-Max rpm for Mandrake and now I have
>>> InnoDB tables, the export works and for now I am happy with it.
>>
>> It's a bug introduced in MySQL 4.0.21 that will be fixed in 4.0.22.
>>
>> http://dev.mysql.com/doc/mysql/en/News-4.0.22.html
> I see: The reason then why the MySQL-Max rpm (obtained from my Mandrake
> urpmi sources) works is that it's version 4.0.15!
>
> I had actually tried to get an earlier version from mysql.com to try
> with that, but couldn't find any. Is there a way to get earlier 
> versions
> in cases such as these?

Also note that the work around described in that bug works successfully 
avoids it.

<http://bugs.mysql.com/bug.php?id=5538?>

So you can continue using mysqldump and InnoDB with 4.0.21 as long as 
you use --single-transaction.  We replaced our --opt flag with:

--add-drop-table --add-locks --all --single-transaction --disable-keys 
--extended-insert --quick

and things are working fine.

--Ware
Thread
mysqldump --opt crashes server on InnoDB tablesThomas Plümpe24 Sep
  • Re: mysqldump --opt crashes server on InnoDB tablesTobias Asplund27 Sep
    • Re: mysqldump --opt crashes server on InnoDB tablesThomas Plümpe27 Sep
      • Re: mysqldump --opt crashes server on InnoDB tablesPaul DuBois27 Sep
        • Re: mysqldump --opt crashes server on InnoDB tablesThomas Plümpe27 Sep
          • Re: mysqldump --opt crashes server on InnoDB tablesPaul DuBois27 Sep
          • Re: mysqldump --opt crashes server on InnoDB tablesWare Adams27 Sep
Re: mysqldump --opt crashes server on InnoDB tablesHeikki Tuuri27 Sep