| Bug #48666 | Memory tables + max_heap_table_size can cause replication problems | ||
|---|---|---|---|
| Submitted: | 10 Nov 2009 12:15 | Modified: | 3 Sep 2010 9:50 |
| Reporter: | Victor Kirkebo | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.0.88-bzr, 5.1.41, 5.1.42-bzr | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | Error_code 1114, memory table, table full | ||
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
