There was a bug that "OPTIMIZE of locked and modified MyISAM table,
reported table corruption" before 3.23.53.
I run maintenance crons that include this optimization on fairly big
tables, with no issues reported so far.
You can check table status by running "analyze table <tablename>", check
"Msg_type" and "Msg_text" in your result set.
Carlos
Jeff
<jsiegel1 at optonli To: "'NYPHP Talk'" <talk at lists.nyphp.org>
ne.net> cc:
Sent by: Subject: [nycphp-talk] MySQL table optimization
talk-bounces at list
s.nyphp.org
08/28/2003 10:18
AM
Please respond to
NYPHP Talk
I have a particular table that has a very large number of deleted
records (and approx. 500 records are deleted and added each day). The
MySQL docs note that running an "Optimize" statement will clean up this
potentially fractured file. However, I believe I had read somewhere (of
course...don't ask me where "somewhere" is...I don't remember) that
there is the potential that the table itself can become corrupted after
running optimize. Is this true? And if it is true, how can I detect, via
code, that a table has become hosed?
Jeff