[nycphp-talk] MySQL table optimization
jsiegel1 at optonline.net
Fri Aug 29 10:47:21 EDT 2003
Thanks! What would be the msg type/text I would look for? Couldn't find
a list after some Googling and, quite honestly, it's not real obvious
from errmsg.txt. However, the only things that seemed "remotely"
possible in errmsg.txt are the following:
"Table '%-.64s' is marked as crashed and should be repaired",
"Table '%-.64s' is marked as crashed and last (automatic?) repair
From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
On Behalf Of Carlos A Hoyos
Sent: Thursday, August 28, 2003 10:25 AM
To: NYPHP Talk
Subject: Re: [nycphp-talk] MySQL table optimization
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.
<jsiegel1 at optonli To: "'NYPHP Talk'"
<talk at lists.nyphp.org>
Sent by: Subject: [nycphp-talk]
MySQL table optimization
talk-bounces at list
Please respond to
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?
talk mailing list
talk at lists.nyphp.org
More information about the talk