Matt England wrote:
...so then I did some googling on "mysql errno
145" and found this
reference:
http://www.karakas-online.de/forum/viewtopic.php?t=332
...and then followed the recommendations there to do the following
stuff, which seems to have cleared up my problem. (*whew*)
Is it fair to assume that database-table corruption (particularly the
indeces) can be a common issue, particularly during an ungraceful (in my
case 'kill -9') database shutdown?
Error 145 is:
145 = Table was marked as crashed and should be repaired
MySQL's old MyISAM table type is not designed to automatically recover
from crashes and other irregular system shutdowns. A table that's not
closed regularly is left with a marker indicating it was left open, and
the system requires you to run an integrity check when it's back online
before continuing.
This may sound familiar from CHKDSK/Scandisk on MS-DOS/Windows or fsck
on older Unix/Linux filesystems; it's the same basic way of doing things.
If you switch your tables to the InnoDB table type, they will recover
more gracefully and automatically from a crash (except in certain really
nasty cases where your hardware is conspiring against you).
Note that the searchindex table must be MyISAM because InnoDB doesn't
support the full text indexing it uses, but every other table can be InnoDB.
-- brion vibber (brion @
pobox.com)