Browse Source

Fix buildbot failure: take into account that there is no optimizer_switch flag

for table elimination in debug builds.
(part 2)
pull/374/head
Sergey Petrunya 16 years ago
parent
commit
0cf5145dee
  1. 2
      mysql-test/r/subselect_sj.result
  2. 2
      mysql-test/r/subselect_sj_jcl6.result
  3. 1
      mysql-test/t/subselect_sj.test

2
mysql-test/r/subselect_sj.result

@ -202,7 +202,7 @@ BUG#37120 optimizer_switch allowable values not according to specification
select @@optimizer_switch;
@@optimizer_switch
index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_condition_pushdown=on,firstmatch=on,loosescan=on,materialization=on,semijoin=on,table_elimination=on
index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_condition_pushdown=on,firstmatch=on,loosescan=on,materialization=on,semijoin=on
set optimizer_switch='default,materialization=off';
select @@optimizer_switch;
@@optimizer_switch

2
mysql-test/r/subselect_sj_jcl6.result

@ -206,7 +206,7 @@ BUG#37120 optimizer_switch allowable values not according to specification
select @@optimizer_switch;
@@optimizer_switch
index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_condition_pushdown=on,firstmatch=on,loosescan=on,materialization=on,semijoin=on,table_elimination=on
index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_condition_pushdown=on,firstmatch=on,loosescan=on,materialization=on,semijoin=on
set optimizer_switch='default,materialization=off';
select @@optimizer_switch;
@@optimizer_switch

1
mysql-test/t/subselect_sj.test

@ -96,6 +96,7 @@ explain extended select * from t1 where a in (select pk from t10 where pk<3);
--echo BUG#37120 optimizer_switch allowable values not according to specification
--echo
--replace_regex /,table_elimination=on//
select @@optimizer_switch;
set optimizer_switch='default,materialization=off';

Loading…
Cancel
Save