| Bug #68775 | GTID_PURGED variable makes mysql dump non backward compatible | ||
|---|---|---|---|
| Submitted: | 26 Mar 2013 9:22 | Modified: | 26 Mar 2013 19:17 |
| Reporter: | Oli Sennhauser | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
| Version: | 5.6.10 | OS: | Any (linux) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | dump, GTID_PURGED, 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
