| Bug #84195 | innodb_ft_result_cache_limit default of 2G seems obscenely high | ||
|---|---|---|---|
| Submitted: | 13 Dec 2016 22:14 | Modified: | 14 Dec 2016 9:22 |
| Reporter: | Rick James | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: FULLTEXT search | Severity: | S3 (Non-critical) |
| Version: | 5.6.13, 5.6.35, 5.7.17 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | innodb FULLTEXT innodb_ft_result_cache_limit default memory | ||
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
