[MDEV-5337] Wrong result in mariadb 5.5.32 with ORDER BY + LIMIT when index_condition_pushdown=on Created: 2013-11-26 Updated: 2014-01-29 Resolved: 2014-01-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.33a, 5.5.34, 10.0.6 |
| Fix Version/s: | 5.5.35, 10.0.8, 5.3.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Zhixin Zhang | Assignee: | Sergei Petrunia |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | innodb, optimizer | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
The query following:
when the set (...) is large and the limit offset is big enough like 20000, then it will return wrong result that here the value of column bid is not in the where condition. And if I turn off the index_condition_pushdown, it will return correct result. Note: I tested it in mariadb 5.5.33a, 5.5.34, 5.5.32 and 10.0.6, all these version have the issue. Also, the issue only occurs in innodb/xtradb. Myisam does not have this issue. How to repeat: Test case: The test case do the following: run the two test cases: |
| Comments |
| Comment by Elena Stepanova [ 2013-11-26 ] |
|
Thanks for reporting and for the test case. |
| Comment by Sergei Petrunia [ 2014-01-24 ] |
|
Debugged, this is the same issue as |
| Comment by Sergei Petrunia [ 2014-01-24 ] |
|
Thanks for the bug report, and for the detailed testcase. The fix is pushed into 5.3 and 5.5 trees, and will be available in the next releases. |
| Comment by Sergei Petrunia [ 2014-01-24 ] |
|
One fix for this issue and |
| Comment by Elena Stepanova [ 2014-01-26 ] |
|
Re-opening just to change Resolution from 'Duplicate' to the more appropriate 'Fixed' |
| Comment by Daniel Bartholomew [ 2014-01-29 ] |
|
http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/2502.567.187 |
| Comment by Daniel Bartholomew [ 2014-01-29 ] |
|
http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/4026.1.1 |