Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
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.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: problems in range_vs_index_merge_innodb.test
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
Re: problems in range_vs_index_merge_innodb.test
Fixed the problem with "Wrong count for key". Pushed the fix into the 5.3 tree.
Re: problems in range_vs_index_merge_innodb.test
Fix released with 5.3.5-ga.
Launchpad bug id: 928352
Re: problems in range_vs_index_merge_innodb.test
The server hits the above assertion when executing the test case for bug #891953 from range_vs_index_merge_innodb.test