Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
For some reason mysqldump has by default max_allowed_packet 24MB.
If you have one field bigger than 24MB, then mysqldump will drop connection in the middle of packet and server will see "connection reset by peer" error.
User has basically no idea, what is causing this error.
24MB seems to be too small default value.
For example mysql client has default max_allowed_packet 1GB.
Yes, it is possible to increase this value from commandline parameter, but as there is no proper error message and user does not know what's the problem causing this error.
I suggest, we should increase mysqldump default value to 1GB, the same as mysql client.
Attachments
Activity
serg, and you would agree to do this change of the default also for current GA versions?
yes, because I cannot think of any negative effects of this change. Except that the client will use more memory instead of aborting in the middle of a big dump. But it's probably a good thing. Those who are short on memory likely set max_allowed_packet anyway and don't rely on a default.
Sure. I don't see any drawbacks from increasing the default.
May be we should do it in other clients too, e.g. it'd be unexpected if mysqldump could produce a dump that mysql cannot restore.