Bug #70245 incorrect costing for range scan causes optimizer to choose incorrect index
Submitted: 4 Sep 2013 21:45 Modified: 5 Sep 2013 16:57
Reporter: trevor price Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Optimizer Severity:S2 (Serious)
Version:5.6.13 OS:Linux (2.6.16.33-xenU x86_64)
Assigned to: Jørgen Løland CPU Architecture:Any
Tags: optimizer cost range_scan

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[4 Sep 2013 21:48] trevor price
Query trace on 5.6.13

Attachment: querytrace.rtf (text/rtf), 15.75 KiB.