[MDEV-6657] Poor plan choice for ORDER BY key DESC optimization and possible range access Created: 2014-08-28  Updated: 2018-11-13  Resolved: 2014-10-06

Status: Closed
Project: MariaDB Server
Component/s: Optimizer
Affects Version/s: 10.0.13
Fix Version/s: 10.1.1

Type: Bug Priority: Major
Reporter: Sergei Petrunia Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: optimizer, order-by-optimization

Issue Links:
Relates
relates to MDEV-6846 Test tokudb_mariadb.mdev6657 fails in... Closed

 Description   

A case reported by stephanevaroqui.

Unfortunately the most of the data is from a customer and is private.

will post here as private comments.

 Comments   
Comment by Sergei Petrunia [ 2014-09-02 ]

Commit is here: http://lists.askmonty.org/pipermail/commits/2014-September/006480.html

Comment by jocelyn fournier [ 2014-09-02 ]

Hi Sergei,

Does this fix impact as well https://mariadb.atlassian.net/browse/MDEV-626 ?

Thanks,
Jocelyn

Comment by Sergei Petrunia [ 2014-09-02 ]

the patch was pushed to https://github.com/MariaDB/server/tree/bb-10.1-mdev6657.

Comment by Sergei Petrunia [ 2014-09-02 ]

jocel1, I'll check.

Comment by Sergei Petrunia [ 2014-09-03 ]

Hi Jocelyn,

MDEV-465 and MDEV-626 are fixed not by this fix, but by fix for MDEV-6384. I've commented at MEV-465. Fix for MDEV-6384 is currently going through QA.

Comment by Sergei Petrunia [ 2014-09-09 ]

Merged this fix with the latest ORDER BY fixes in 10.1, pushed to https://github.com/MariaDB/server/tree/bb-10.1-mdev6657-r2

Generated at Thu Feb 08 07:13:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.