Hello Tommy!
> We suspect that the problem is related to the fact that we delete ~7000
> rows and inserts the same shortly thereafter. The mysql-manual mentions
> that you should run an "optimize table" after deleting many rows from a
> table, but doesn't list it as an requirement.
If you're hav
We've had problems for a few months with corruption of a MyISAM table,
when deleting many rows. The same setup/code didn't have problems under
3.22.x but started when we switched to 3.23.x - we're now running 3.23.40.
The table is used by a mod_perl application serving webpages running on
the
