| 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: | |
| 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 | ||
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
[14 Apr 2017 9:37]
Laurynas Biveinis
[4 Aug 2017 19:40]
Laurynas Biveinis
Bug 84366 fix for 8.0.2
Attachment: bug84366-8.0.2.patch (application/octet-stream, text), 14.42 KiB.
[13 Jun 2018 12:19]
Laurynas Biveinis
Bug 84366 fix for 8.0.11
Attachment: bug84366-8.0.11.patch (application/octet-stream, text), 14.57 KiB.
