MySQL Bugs: #65149: Removed enable-locking option is still listed in 5.5 manual without description

Bug #65149	Removed enable-locking option is still listed in 5.5 manual without description
Submitted:	30 Apr 2012 1:36	Modified:	5 Jun 2012 15:54
Reporter:	Elena Stepanova	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.5	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
enable-locking option was deprecated in 5.1 and removed in 5.5.

Server option and variable reference in 5.1 and 5.5 manual (http://dev.mysql.com/doc/refman/5.5/en/mysqld-option-tables.html) contains enable-locking listed as a valid command-line or option-file entry. The link in fact points at 'external-locking' section, which, however, does not say that enable-locking was removed in favor of external-locking (does not say anything at all about enable-locking).

While with 5.1 it is at least obvious from the server error log (as it says that the option is deprecated), it becomes quite confusing with 5.5, which aborts with the generic 'unknown option' error, and requires some digging to figure out what happened and why a seemingly viable option is not accepted.

How to repeat:
See http://dev.mysql.com/doc/refman/5.5/en/mysqld-option-tables.html, search for enable-locking.

Suggested fix:
Either a) remove the option from the reference list, or b) create a section for enable-locking which would say that the option was removed in 5.5, or c) add a note in external-locking section that the option is to be used instead of the old and removed enable-locking.

Thank you for the bug report.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

I'll add an explicit stub entry for this option that says it's deprecated and --external-locking should be used instead.