Bug #87947 Optimizer chooses ref over range when access when range access is faster
Submitted: 3 Oct 2017 4:00 Modified: 9 Oct 2017 5:36
Reporter: Jaime Sicam Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Optimizer Severity:S5 (Performance)
Version:5.7.19 OS:Any
Assigned to: CPU Architecture:Any

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:

[3 Oct 2017 4:02] Jaime Sicam
test data

Attachment: t2.sql (application/octet-stream, text), 315.82 KiB.

[8 Oct 2017 5:22] Jaime Sicam
New test data for t2

Attachment: t2-1.sql (application/octet-stream, text), 1.06 KiB.

[9 Oct 2017 5:42] Umesh Shastry
test results - 5.7.19

Attachment: 87947_5.7.19.results (application/octet-stream, text), 11.08 KiB.