MySQL Bugs: #52343: Randgen simplified test cases need revamping of output variable setttings

Bug #52343	Randgen simplified test cases need revamping of output variable setttings
Submitted:	24 Mar 2010 20:23	Modified:	26 Mar 2010 12:10
Reporter:	Patrick Crews	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Tools: Random Query Generator	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Bernt Marius Johnsen	CPU Architecture:	Any

Description:
The variables included in the Randgen's simplified test cases are no longer totally relevant for all builds, most notably 6.0-codebase:

Current output:
/* Server0: MySQL 6.0.14-alpha-gcov-debug-log */

/*!50400 SET SESSION optimizer_switch = 'index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,engine_condition_pushdown=on,firstmatch=on,loosescan=on,materialization=on,semijoin=on,mrr=on,mrr_cost_based=off,index_condition_pushdown=on' */;
/*!50400 SET SESSION optimizer_use_mrr = '' */;
/*!50400 SET SESSION engine_condition_pushdown = 'ON' */;
/*!50400 SET SESSION join_cache_level = '' */;
/*!50400 SET SESSION debug = '' */;

Note that optimizer_use_mrr and engine_condition_pushdown have been moved to switches within optimizer_switch and that join_cache_level is now optimizer_join_cache_level.

How to repeat:
Run a grammar against the 6.0-codebase-bugfixing tree.  At the time of this writing, optimizer_subquery is producing some interesting crashes that can be simplified and optimizer_no_subquery is producing some diff's when compared to 5.1-bugteam.

Bernt, while you are at it, can you also please add EXPLAIN output to the MTR test case. It does not have to be anything fancy, just remotely readable.

The Optimizer team can provide you with extra information as to what variables are currently the important ones to dump.

Fixed.