| Bug #107293 | CURRENT_TIMESTAMP not safe after all? | ||
|---|---|---|---|
| Submitted: | 15 May 2022 13:34 | Modified: | 21 May 2022 20:52 |
| Reporter: | Przemyslaw Malkowski | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
| Version: | 5.7.37, 8.0.28 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | current_timestamp, mixed | ||
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
