| Bug #25966 | 2MB per second endless memory consumption after LOCK TABLE ... WRITE | ||
|---|---|---|---|
| Submitted: | 31 Jan 2007 7:03 | Modified: | 16 Mar 2007 17:52 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Locking | Severity: | S1 (Critical) |
| Version: | <=5.0.36, 5.1 | OS: | Windows (windows, linux) |
| Assigned to: | Dmitry Lenev | CPU Architecture: | Any |
| Tags: | bfsm_2007_02_15, bfsm_2007_03_01, lock table write, memory leak | ||
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
[4 Mar 2007 22:50]
Shane Bester
