| Bug #98717 | generated column causes mysqldump to create extremely big dump file | ||
|---|---|---|---|
| Submitted: | 23 Feb 2020 14:57 | Modified: | 24 Feb 2020 5:37 |
| Reporter: | Christian Roser | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: mysqldump Command-line Client | Severity: | S1 (Critical) |
| Version: | 5.7.x, 5.7.29 | OS: | Debian |
| Assigned to: | CPU Architecture: | x86 | |
| Tags: | corruption, generated column, invalid data, mysqldump | ||
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
