Bug #84366 InnoDB index dives do not detect concurrent tree changes, return bogus estimates
Submitted: 29 Dec 2016 6:39 Modified: 1 Feb 2018 10:51
Reporter: Laurynas Biveinis (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.6+ OS:Any
Assigned to: CPU Architecture:Any
Tags: index dive, innodb, range optimizer

A contribution for this bug was already accepted. No new contributions can be submitted.

[17 Jan 2017 4:17] Laurynas Biveinis 
Bug 84366 fix for 5.6

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Attachment: bug84366-5.6.patch (application/octet-stream, text), 14.06 KiB.
[17 Jan 2017 4:17] Laurynas Biveinis 
Bug 84366 fix for 5.7

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Attachment: bug84366-5.7.patch (application/octet-stream, text), 11.12 KiB.
[17 Jan 2017 4:17] Laurynas Biveinis 
Bug 84366 fix for 8.0.0

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Attachment: bug84366-8.0.patch (application/octet-stream, text), 11.12 KiB.