MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:September 3 1999 9:40am
Subject:periodically corrupt index
View as plain text  
>>>>> "Andrey" == Andrey Kotrekhov <kota@stripped> writes:

Andrey> Hi!
Andrey> I use big table >1000000 records
Andrey> it contain statistics.
Andrey> every day I rotate old value.
Andrey> But sometimes I get error - my index corrupted :(
Andrey> Why?
Andrey> I do standart operation
Andrey> DELETE FROM traffic WHERE ...
>> From this DELETE I wont delete near 100000 records every day.

Andrey> I use FreeBSD2.2.8-STABLE & mysql-3-22.25


Table rotation should not corrupt indexes.  To be able to help you I
would need a lot more information.

You can find information how to do a correct bug report at:

PLEASE read the above before reposting your question, this will save us all
a lot of time!

Please read also the section 'Debugging the MySQL server' about how to 
be able to replicate this so that we can find and fix the problem!

SQL_BIG_TABLES=1 doesn't fix "table full" error 1114Christopher Lee3 Sep
  • periodically corrupt indexAndrey Kotrekhov3 Sep
    • periodically corrupt indexMichael Widenius3 Sep
  • SQL_BIG_TABLES=1 doesn't fix "table full" error 1114Michael Widenius3 Sep
    • ODBC-Error map to MYSQL-error.Jagadish R.R.( ASI 99)3 Sep
  • Re:SQL_BIG_TABLES=1 doesn't fix "table full" error 1114sinisa3 Sep
Re: SQL_BIG_TABLES=1 doesn't fix "table full" error 1114Richard Ellerbrock3 Sep