Closed Bug 1107310 Opened 11 years ago Closed 11 years ago

Mention max_allowed_packet in mysqldump section

Categories

(Bugzilla :: Documentation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 5.0

People

(Reporter: gerv, Assigned: gerv)

Details

Attachments

(1 file, 1 obsolete file)

http://bugzilla.readthedocs.org/en/latest/installing/backups.html - section 3.10.1.1 should mention the max_allowed_packet parameter that you sometimes need on the command line to do a mysqldump. Gerv
Attached patch Patch v.1 (obsolete) — Splinter Review
Assignee: documentation → gerv
Status: NEW → ASSIGNED
Attachment #8569210 - Flags: review?(LpSolit)
Comment on attachment 8569210 [details] [diff] [review] Patch v.1 >+:command:`mysqldump --opt --max-allowed-packet=16M -u $USERNAME -p $DATABASENAME > backup.sql` No need to pass --opt. It's enabled by default. Also, the default value for max-allowed-packet is 24MB. It's a bit weird to ask admins to use a lower value when doing backups.
(In reply to Frédéric Buclin from comment #2) > Comment on attachment 8569210 [details] [diff] [review] > Patch v.1 > > >+:command:`mysqldump --opt --max-allowed-packet=16M -u $USERNAME -p $DATABASENAME > backup.sql` > > No need to pass --opt. It's enabled by default. OK. > Also, the default value for > max-allowed-packet is 24MB. It's a bit weird to ask admins to use a lower > value when doing backups. 16M is the value we suggest in the install docs, which is why I'm using it as the example here. I too thought the default value was higher, and so hoped to eliminate the requirement to set it entirely from the docs, but then I was told that it varied from distribution to distribution. Is there any harm in setting it to way higher than the DB uses? E.g. 512M? Gerv
(In reply to Gervase Markham [:gerv] from comment #3) > Is there any harm in setting it to way higher than the DB uses? E.g. 512M? (Almost) nobody wants to store attachments as large as 512MB in the DB. Just set it to 24MB or 32MB if you want a sensible example.
Comment on attachment 8569210 [details] [diff] [review] Patch v.1 Please fix comment 4.
Attachment #8569210 - Flags: review?(LpSolit)
Attached patch Patch v.2Splinter Review
Attachment #8569210 - Attachment is obsolete: true
Attachment #8570460 - Flags: review?(LpSolit)
Comment on attachment 8570460 [details] [diff] [review] Patch v.2 I didn't try to compile the documentation, but it looks good. r=LpSolit
Attachment #8570460 - Flags: review?(LpSolit) → review+
Target Milestone: --- → Bugzilla 5.0
Flags: approval?
Flags: approval?
Flags: approval5.0+
Flags: approval+
To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git b7147b7..c33b98d master -> master To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git c1fa559..dd15f45 5.0 -> 5.0 Gerv
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: