| Bug #53893 | RBR: nullable unique key can lead to out-of-sync slave | ||
|---|---|---|---|
| Submitted: | 21 May 2010 17:44 | Modified: | 14 Oct 2010 12:32 |
| Reporter: | Luis Soares | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Row Based Replication ( RBR ) | Severity: | S3 (Non-critical) |
| Version: | 5.1.48-bzr | OS: | Any |
| Assigned to: | Luis Soares | CPU Architecture: | Any |
| Tags: | INDEX, RBR, unique key | ||
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
