----- Original Message ----- From: "Benjamin Pflugmann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Mark" <[EMAIL PROTECTED]> Sent: Saturday, May 11, 2002 7:24 PM Subject: Re: How dangerous is OPTIMIZE TABLE?
> Hi. > > This is more intended to be an second answer to the original post, but I > don't have it anymore. > > On Fri, May 10, 2002 at 11:00:56AM -0700, [EMAIL PROTECTED] wrote: > > > On Fri, May 10, 2002 at 12:55:39PM +0200, Mark wrote: > > > > > How dangerous is OPTIMIZE TABLE? > > > > > > I have been reading through the FAQ, and came to the section on > > > OPTIMIZE TABLE. > > > > > > http://www.mysql.com/doc/O/P/OPTIMIZE_TABLE.html [...] > > > > I use it pretty often and have never experienced any problems. > > Usually when there are problems with data corruption, it is something > > outside of MySQL (OS or hardware problems). > > I had a look at the comment and the cited error number is simply a > "disk full" condition. And on the second cited error number is a "last > repair failed" error. > > So it is not dangerous in any way. Copying back the original files > (which MySQL renamed) would have solved the problem at once. Thank you very much; you put my mind to rest. :) P.S. You would think that people allowed to add comments to the online manual, know whereof they speak. Thanks! - Mark --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
