List:General Discussion« Previous MessageNext Message »
From:Albert Braun Date:April 26 1999 3:30pm
Subject:about --skip-locking
View as plain text  

The MySQL manual says: The --skip-locking option disables file locking
between SQL requests. This gives greater speed but has the following
consequences: You MUST flush all tables with mysqladmin flush-tables
before you try to check or repair tables with isamchk. (isamchk -d
tbl_name is always allowed, since that simply displays table
information.) You can't run two MySQL servers on the same data files, if
both are going to update the same tables.

But I still have a question: When running just *one* MySQL server, does
--skip-locking affect the table lock associated with updates and
inserts? In other words, when running a single mysqld process, can I
expect --skip-locking to provide any performance improvement on
concurrent updates/inserts to the same table?

Best Regards,
Albert Braun

about --skip-lockingAlbert Braun26 Apr
  • about --skip-lockingMichael Widenius27 Apr