| Bug #78241 | Valgrind reports a memory leak on innodb.create_tablespace | ||
|---|---|---|---|
| Submitted: | 27 Aug 2015 10:24 | Modified: | 1 Sep 2015 9:48 |
| Reporter: | Laurynas Biveinis (OCA) | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.7.8 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | CREATE TABLESPACE, innodb, memory leak, valgrind | ||
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
