| Bug #22017 | Huge memory usage after mysqldump. | ||
|---|---|---|---|
| Submitted: | 5 Sep 2006 12:39 | Modified: | 3 Jul 2013 5:52 |
| Reporter: | Dimitrij HIlt | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S4 (Feature request) |
| Version: | 5.1.11, 5.0.26, 5.0.24-standard-log | OS: | Linux (Linux/Debian ia32/2.6) |
| Assigned to: | Heikki Tuuri | CPU Architecture: | Any |
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
[5 Sep 2006 13:45]
Dimitrij HIlt
[12 Mar 2007 4:08]
Anders Henke
Memory usage with 5.0.37 during dump (starting at 2am)
Attachment: rdb225-mem.gif (image/gif, text), 16.89 KiB.
