problems in range_vs_index_merge_innodb.test

[Sergei Golubchik]

1. run the test. mysqld.1.err will contain

120207 17:27:10 [Note] Use_count: Wrong count for key at 0x3400688, 0 should be 1
120207 17:27:10 [Note] Use_count: Wrong count for key at 0x3400688, 0 should be 1
120207 17:27:10 [Note] Use_count: Wrong count for key at 0x3400688, 0 should be 1
120207 17:27:10 [Note] Use_count: Wrong count for key at 0x3400688, 0 should be 1

2. in storage/innodb_plugin/handler/ha_innodb.cc, records_in_range() method starts from

 DBUG_ASSERT(min_key || max_key);

add the same assert to xtradb. run the test. the assert will fire.

[Igor Babaev (igorb-seattle)]

The server hits the above assertion when executing the test case for bug #891953 from range_vs_index_merge_innodb.test

[Igor Babaev (igorb-seattle)]

The complains about "Wrong count for key" are issued when the test case for bug #800184 from range_vs_index_merge_innodb.test is executed

[Igor Babaev (igorb-seattle)]

Fixed the problem with "Wrong count for key". Pushed the fix into the 5.3 tree.

[Elena Stepanova (elenst)]

Fix released with 5.3.5-ga.