Bug #43527 Maria returns no rows on multi range access with limit clause
Submitted: 10 Mar 2009 6:22 Modified: 7 May 2009 8:34
Reporter: Nidhi Shrotriya Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Maria storage engine Severity:S3 (Non-critical)
Version:6.0.11 OS:Any
Assigned to: Guilhem Bichot CPU Architecture:Any
Triage: Triaged: D2 (Serious)

[10 Mar 2009 6:22] Nidhi Shrotriya
Description:
CREATE TABLE t2(c1 TINYINT UNSIGNED NOT NULL, c2 TINYINT NULL, c3 SMALLINT, c4 MEDIUMINT , c5 INT, c6 INTEGER, c7 BIGINT, PRIMARY KEY(c1,c6));
CREATE TABLE t3(c1 TINYINT UNSIGNED NOT NULL, c2 TINYINT NULL, c3 SMALLINT, c4 MEDIUMINT , c5 INT, c6 INTEGER, c7 BIGINT, index idx(c2,c7));

With Other Engines:
SELECT * FROM t2 WHERE c1 >= 0 AND c1 < 115 AND c6 = 113 ORDER BY c1,c6;
c1      c2      c3      c4      c5      c6      c7
102     -109    110     111     112     113     114
103     -109    110     111     112     113     114
108     -109    110     111     112     113     114
SELECT * FROM t2 WHERE c1 >= 0 AND c1 < 115 AND c6 = 113 ORDER BY c1,c6 LIMIT 2;
c1      c2      c3      c4      c5      c6      c7
102     -109    110     111     112     113     114
103     -109    110     111     112     113     114

With Maria:
SELECT * FROM t2 WHERE c1 >= 0 AND c1 < 115 AND c6 = 113 ORDER BY c1,c6;
c1      c2      c3      c4      c5      c6      c7
102     -109    110     111     112     113     114
103     -109    110     111     112     113     114
108     -109    110     111     112     113     114
SELECT * FROM t2 WHERE c1 >= 0 AND c1 < 115 AND c6 = 113 ORDER BY c1,c6 LIMIT 2;
c1      c2      c3      c4      c5      c6      c7

With other engines:
SELECT * FROM t3 WHERE c2 >= -123 AND c2 < 0 AND c7 = 121 ORDER BY c2,c7;
c1      c2      c3      c4      c5      c6      c7
115     -116    117     118     119     120     121
SELECT * FROM t3 WHERE c2 >= -123 AND c2 < 0 AND c7 = 121 ORDER BY c2,c7 LIMIT 2;
c1      c2      c3      c4      c5      c6      c7
115     -116    117     118     119     120     121

With Maria:
SELECT * FROM t3 WHERE c2 >= -123 AND c2 < 0 AND c7 = 121 ORDER BY c2,c7;
c1      c2      c3      c4      c5      c6      c7
115     -116    117     118     119     120     121
SELECT * FROM t3 WHERE c2 >= -123 AND c2 < 0 AND c7 = 121 ORDER BY c2,c7 LIMIT 2;
c1      c2      c3      c4      c5      c6      c7

Same with DESC.

How to repeat:
As mentioned in Description.
[10 Mar 2009 6:42] Sveta Smirnova
Thank you for the report.

Please provide dump of tables t2 and t3.
[10 Mar 2009 7:47] Nidhi Shrotriya
Test Case

Attachment: insert_number_bug_maria_43527.test (application/octet-stream, text), 1.64 KiB.

[10 Mar 2009 7:49] Nidhi Shrotriya
Please find attached the testcase.
[10 Mar 2009 8:36] Sveta Smirnova
Thank you for the feedback.

Verified as described.
[10 Mar 2009 10:09] Nidhi Shrotriya
Happens with all int types.
[12 Mar 2009 9:18] Guilhem Bichot
goes away when removing HA_DO_INDEX_COND_PUSHDOWN from ha_maria.h
[13 Mar 2009 14:11] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/69152

2726 Guilhem Bichot	2009-03-13
      Fix for multiple symptoms sharing the same cause:
      BUG#42297 Maria: crash in multi-range-read code
      BUG#42298 Maria: SELECT with join returns no rows
      BUG#42299 Maria: SELECT using cp1251-table returns no rows
      BUG#42681 Maria returns duplicate rows with range access on 'date type
      BUG#42683 Maria returns wrong results for <= NULL and <> NULL 
      BUG#43527 Maria returns no rows on multi range access with limit clause
      BUG#43530 Maria has Issues with range select <>, < with -ve range values on signed index
      BUG#43552 Maria returned wrong rows with range access on float
      BUG#43620 Maria throws 'Got error 176 from storage engine' on a range query
      BUG#43623 Maria returns no rows with date index on range access >, >=, BETWEEN
     @ mysql-test/suite/maria/r/maria.result
        after fixing the bug, we can see one more row in the result. Ah, if we had paid attention
        to maria.result when we added this straight_join test, we would have caught the bug immediately.
     @ mysql-test/suite/maria/r/maria4.result
        result
     @ mysql-test/suite/maria/t/maria4.test
        test for fixed bugs. All its pieces would fail (errno 176, missing rows, too many rows) without the entire
        bugfix of ma_rkey.c
     @ storage/maria/ma_rkey.c
        Because of missing (), icp_res was inverted compared to the result of
        ma_check_index_cond(), which wasn't desired (0==0 -> 1, 1==0 -> 0). We would go
        to "err:" wrongly and thus pick up the value of my_errno which was left from previous
        functions (for example, 176 left by the ha_tina CSV log write at start of statement!);
        sometimes the errno would be returned to client, sometimes it would just cause
        a matching row to be missed.
        This fixed BUG#42297 BUG#42298. But was not enough for BUG#43552:
        - icp_res==2 was not converted to "key not found", causing non-matching rows to be returned.
        Now the usage of icp_res is closer to ma_rnext.c and ma_rnext_same.c.
[3 Apr 2009 14:52] Bugs System
Pushed into 6.0.11-alpha (revid:guilhem@mysql.com-20090402210815-lu17n4kj8c73cfe8) (version source revid:guilhem@mysql.com-20090313141043-73a6mr7hsrqm3djc) (merge vers: 6.0.11-alpha) (pib:6)
[7 May 2009 8:34] MC Brown
A note has been added to the 6.0.11 changelog: 

Running a SELECT on a multi-range query with a LIMIT clause on a Maria table could return invalid result sets.