MySQL - what does skip-locking in my.cnf do?

tags:

mysql

views:

3156

answers:

MySQL - what does skip-locking in my.cnf do?

I'm using MySQL 5.0.67 on RHEL5 and basing my configuration on my-huge.cnf.

I can't find anything in the MySQL manual for the row 'skip-locking' which appears in the config file.

Should this be replaced with 'skip_external_locking' or should I just remove the row entirely as that is now a default.

MySQL Manual for skip-external-locking

Thanks.

+1 A:

see http://dev.mysql.com/doc/refman/5.0/en/external-locking.html

quote:

If you run multiple servers that use the same database directory (not recommended), each server must have external locking enabled.

It really just has to do with the dangers presented by multiple processes accessing the same data. In many DBMS situations you want to lock the table/row before performing an operation, and unlocking afterwards. This is to prevent possible data corruption.

Edit: see http://dev.mysql.com/doc/refman/4.1/en/news-4-0-3.html Quote

Renamed --skip-locking to --skip-external-locking.

Jonathan Fingland 2009-06-03 09:02:59

Thanks - but that's skip_external_locking - I'd like to know if 'skip-locking' is the same thing, and if is necessary in the config file because it is already a default?

Richard 2009-06-03 09:08:46

edited. it was just a rename

Jonathan Fingland 2009-06-03 11:43:52

Thanks again, so to summarise - the 'skip-locking' row of the config file can be removed because a) it is out of date, the variable has been renamed. b) that behaviour is the default anyway

Richard 2009-06-03 12:37:26

ansaurus

tags:

views:

answers:

MySQL - what does skip-locking in my.cnf do?

related questions