Bug #89650 | Incorrect ordering with memory tables and long keys | ||
---|---|---|---|
Submitted: | 13 Feb 2018 13:55 | Modified: | 14 Feb 2018 6:41 |
Reporter: | Zsolt Parragi (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.7, 8.0, 5.6.39, 5.7.21 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[13 Feb 2018 13:55]
Zsolt Parragi
[13 Feb 2018 14:39]
Zsolt Parragi
It's possible that this is intended behavior, but it is definitely misleading: the problem is that the max_sort_length variable defaults to 1024, while the max key length is 3072. This means that fields between these will be correctly sorted when the server is using an index, but won't be otherwise.
[14 Feb 2018 6:41]
MySQL Verification Team
Hello Zsolt Parragi, Thank you for the report. Thanks, Umesh