I have read that --skip-locking is enabled by default on Linux systems
because of a bug in the Linux file locking mechanism. This leads me to
wonder about when locking is important with MySQL.
I have one MySQL daemon running on Slackware Linux 2.2.5. There are several
tables and many client machines, but there are two clients that both INSERT
into the same large (+3 million records) table multiple times per second.
This table becomes corrupt somewhat regularly. Is there potentially a
problem with more than one MySQL thread updating the table at the same time?
Or does MySQL handle preventing this sort of problem?
Socket Internet Services
Columbia, MO, US