[MDEV-3750] LP:928352 - problems in range_vs_index_merge_innodb.test Created: 2012-02-07  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sergei Golubchik Assignee: Igor Babaev
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug928352.xml    

 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.

 Comments   
Comment by Igor Babaev [ 2012-02-07 ]

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

Comment by Igor Babaev [ 2012-02-08 ]

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

Comment by Igor Babaev [ 2012-02-17 ]

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.

Comment by Elena Stepanova [ 2012-03-18 ]

Re: problems in range_vs_index_merge_innodb.test
Fix released with 5.3.5-ga.

Comment by Rasmus Johansson (Inactive) [ 2012-03-18 ]

Launchpad bug id: 928352

Generated at Thu Feb 08 06:50:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.