| Bug #45236 | large blob inserts from mysqldump fail, possible memory issue ? | ||
|---|---|---|---|
| Submitted: | 1 Jun 2009 8:46 | Modified: | 17 Jul 2009 3:33 |
| Reporter: | Chris Anders | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: mysqldump Command-line Client | Severity: | S1 (Critical) |
| Version: | 5.0.81 & 5.1.34 | OS: | FreeBSD (6.3) |
| Assigned to: | Alexey Kopytov | CPU Architecture: | Any |
| Tags: | regression | ||
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
[1 Jun 2009 8:48]
Chris Anders
[1 Jun 2009 11:43]
Sveta Smirnova
problem dump
Attachment: bug45236_corrupted.sql.bz2 (application/octet-stream, text), 119.65 KiB.
[1 Jun 2009 11:43]
Sveta Smirnova
OK dump
Attachment: bug45236_OK.sql.bz2 (application/octet-stream, text), 119.66 KiB.
