| Bug #95065 | Strange memory management when using full-text indexes | ||
|---|---|---|---|
| Submitted: | 19 Apr 2019 18:05 | Modified: | 30 Apr 2019 14:50 |
| Reporter: | Yura Sorokin (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: FULLTEXT search | Severity: | S3 (Non-critical) |
| Version: | 5.6.43, 5.7.25, 8.0.15, 8.0.16 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
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
[19 Apr 2019 18:07]
Yura Sorokin
[30 Apr 2019 14:52]
Umesh Shastry
8.0.16 - Debian9 with 1 CPU and 12GB Memory, 12 CPU and 12GB Memory results
Attachment: 95065_8.0.16_Debian9.results (application/octet-stream, text), 451.07 KiB.
[30 Apr 2019 14:54]
Umesh Shastry
8.0.16 - Ubuntu 19.04 with 1 CPU and 12GB Memory results
Attachment: 95065_8.0.16.Ubuntu.results (application/octet-stream, text), 206.24 KiB.
