index_merge_innodb test was failed

Bug #586520 reported by Oleg Tsarev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Critical
Unassigned

Bug Description

CURRENT_TEST: main.index_merge_innodb
--- /storage/project/percona/deadlock_fix/Percona-Server/mysql-test/r/index_merge_innodb.result 2010-05-06 18:58:48.000000000 +0300
+++ /storage/project/percona/deadlock_fix/Percona-Server/mysql-test/r/index_merge_innodb.reject 2010-05-27 22:02:59.000000000 +0300
 -111,7 +111,7 @@
 explain select count(*) from t1 where
 key1a = 2 and key1b is null and key2a = 2 and key2b is null;
 id select_type table type possible_keys key key_len ref rows Extra
-1 SIMPLE t1 index_merge i1,i2 i1,i2 10,10 NULL 4 Using intersect(i1,i2); Using where; Using index
+1 SIMPLE t1 index_merge i1,i2 i1,i2 10,10 NULL 3 Using intersect(i1,i2); Using where; Using index
 select count(*) from t1 where
 key1a = 2 and key1b is null and key2a = 2 and key2b is null;
 count(*)
 -119,7 +119,7 @@
 explain select count(*) from t1 where
 key1a = 2 and key1b is null and key3a = 2 and key3b is null;
 id select_type table type possible_keys key key_len ref rows Extra
-1 SIMPLE t1 index_merge i1,i3 i1,i3 10,10 NULL 4 Using intersect(i1,i3); Using where; Using index
+1 SIMPLE t1 index_merge i1,i3 i1,i3 10,10 NULL 3 Using intersect(i1,i3); Using where; Using index
 select count(*) from t1 where
 key1a = 2 and key1b is null and key3a = 2 and key3b is null;
 count(*)

mysqltest: Result content mismatch

Changed in percona-server:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone: none → 11.0
Changed in percona-server:
status: Triaged → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-316

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.