Bug #36716 optimizer_use_mrr: cannot set at server startup, does not appear in help message
Submitted: 14 May 2008 18:29 Modified: 14 May 2008 19:07
Reporter: Paul DuBois
Status: Verified
Category:Server: Optimizer Severity:S3 (Non-critical)
Version:6.0.x OS:Any
Assigned to: Target Version:
Triage: Triaged: D4 (Minor)

[14 May 2008 18:29] Paul DuBois
Description:
The optimizer_use_mrr system variable (added in 5.2.4) is not listed in the server's
my_long_options[] array, and thus cannot be set as a command option at server startup,
and it does not appear in the server's help message.

How to repeat:
Add this to the server's option file:

[mysqld]
optimizer_use_mrr=force

Start the server. It will fail with this error message:

080514 11:22:31 [ERROR] /var/mysql/60006/libexec/mysqld: unknown variable
'optimizer_use_mrr=force'

Suggested fix:
Following the entry for optimizer_search_depth in my_long_options[], add an entry for
optimizer_use_mrr.
[14 May 2008 19:07] Valeriy Kravchuk
Thank you for a bug report. Verified just as described with 6.0.4.

You can set it using "optimizer_use_mrr=force;" as a workaround.
[14 May 2008 19:18] Paul DuBois
Right, the variable can be set at runtime, for either the global or session values. The
scope of this bug report is limited only to setting the variable at server startup.