| Bug #75519 | Potential InnoDB data loss when binary logging is enabled | ||
|---|---|---|---|
| Submitted: | 15 Jan 2015 17:05 | Modified: | 4 Jun 2015 10:05 |
| Reporter: | Davi Arnaut (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 5.6, 5.6.25 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | binary log, data loss, innodb, innodb_flush_log_at_trx_commit | ||
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
[27 Sep 2023 11:55]
Laurynas Biveinis
