Bug #67958 | IMPORTANT! MySQL Server 5.5.29(28) wrong sorting using complex index | ||
---|---|---|---|
Submitted: | 21 Dec 2012 12:53 | Modified: | 18 Jan 2013 11:14 |
Reporter: | Alexander Egelsky | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S1 (Critical) |
Version: | 5.5.29, 5.5.28 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.5.29, 5.5.29, bug, core, INDEX, order by, sorting |
[21 Dec 2012 12:53]
Alexander Egelsky
[21 Dec 2012 12:54]
Alexander Egelsky
Schema to reproduce
Attachment: __schema_5.5.29_bug.sql (application/octet-stream, text), 900 bytes.
[21 Dec 2012 12:55]
Alexander Egelsky
Query which should return 525
Attachment: __query_5.5.29_bug.sql (application/octet-stream, text), 422 bytes.
[21 Dec 2012 13:10]
MySQL Verification Team
Thank you for the report. I tested a few versions and here are my results. 5.1.66 : 525.0000 5.5.8 : 525.0000 5.5.20 : 525.0000 5.5.24 : 525.0000 5.5.25a: 525.0000 5.5.27 : 99.0000 <-- regression ? 5.5.28 : 99.0000 5.5.29 : 99.0000 5.5.30 : 99.0000 5.6.11 : 525.0000
[21 Dec 2012 13:13]
Alexander Egelsky
Hi! Thank you for fast response, yes, the only valid value is 525.0000
[21 Dec 2012 13:57]
MySQL Verification Team
Hi Alexander, please check if this is really a duplicate of a known bug: http://bugs.mysql.com/bug.php?id=67866
[21 Dec 2012 16:27]
Alexander Egelsky
Yep, looks quite the same. The only thing that differs - is if you will remove complex key from `bids` table ( `bid_amt_ordering` ), my bug will vanish. And that guy from bug you showed me didn't used complex keys. Guess these bugs are related, but no clones of each other, I would add some relationship between them.
[7 Jan 2013 14:40]
Olav Sandstå
This is caused by the same issue as reported in Bug#66845.
[18 Jan 2013 11:14]
Olav Sandstå
Closing this bug as duplicate of Bug#66845.