Bug #45727 Parts of index_merge_innodb.test are disabled due to EXPLAIN diffs
Submitted: 24 Jun 2009 19:04
Reporter: Alexander Nozdrin Email Updates:
Status: Verified Impact on me:
None 
Category:Tests: Server Severity:S3 (Non-critical)
Version:5.4 OS:Any
Assigned to: CPU Architecture:Any
Tags: disabled

[24 Jun 2009 19:04] Alexander Nozdrin
Description:
index_merge_innodb.test:

# The first two tests are disabled because of non deterministic explain output.
# If include/index_merge1.inc can be enabled for InnoDB and all other
# storage engines, please remove the subtest for Bug#21277 from
# include/index_merge2.inc.
# This test exists already in include/index_merge1.inc.
# --source include/index_merge1.inc
# --source include/index_merge_ror.inc

How to repeat:
*
[7 Oct 2009 15:34] Alexander Nozdrin
include/index_merge2.inc was disabled too.

It causes the following result mismatch in PB:
@@ -311,7 +311,7 @@
 update t1 set key2=key1,key3=key1;
 explain select * from t1 where (key3 > 30 and key3<35) or (key2 >32 and key2 < 40);
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
-1	SIMPLE	t1	index_merge	i2,i3	i3,i2	4,4	NULL	9	Using sort_union(i3,i2); Using where
+1	SIMPLE	t1	index_merge	i2,i3	i3,i2	4,4	NULL	13	Using sort_union(i3,i2); Using where
 select * from t1 where (key3 > 30 and key3<35) or (key2 >32 and key2 < 40);
 key1	key2	key3
 31	31	31

XRef: http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2368661&...
[18 Jun 2010 9:30] Olav Sandstå
A similar difference in explain output is also reported in Bug#54398.