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:

  • On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
  • On windows use WinZip or a similar utility to split the large file
[4 Sep 2013 21:48] trevor price
Query trace on 5.6.13

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

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.036 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.