From: ludo@gnu.org (Ludovic Courtès)
To: Ben Sturmfels <ben@stumbles.id.au>
Cc: 25415@debbugs.gnu.org
Subject: bug#25415: MySQL "server has gone away" when reloading database dump due to "max_allowed_packet" default
Date: Thu, 12 Jan 2017 15:22:39 +0100 [thread overview]
Message-ID: <87wpe02w9c.fsf@gnu.org> (raw)
In-Reply-To: <20170111111003.5e8ae2c8@stumbles.id.au> (Ben Sturmfels's message of "Wed, 11 Jan 2017 11:10:03 +1100")
Hi Ben,
Ben Sturmfels <ben@stumbles.id.au> skribis:
> Reloading the same dump works for me on default MySQL in Trisquel 7.
> The database dump was created on Debian with `mysqldump --no-create-db
> DBNAME`.
>
> On Guix, I was able to reload the dump by running mysqld with a custom
> config file with max_allowed_packet=16M under [mysqld].
>
> It appears that the default value for `max_allowed_packet` under
> Debian/Trisquel is "16M", where under Guix it is "4M". The mysqldump
> defaults bunche a whole lot of records into a single insert statement
> for performance, which is why I'm getting a value > 4M.
>
> Could it be worth setting max_allowed_packet to 16M in Guix's
> `mysql-configuration-file` function for consistency with Debian?
Definitely. I would add a ‘max-allowed-packet’ field in
<mysql-configuration> in (gnu services databases) and make sure it’s
honored.
Would you like to give it a try?
Thanks for your report!
Ludo’.
next prev parent reply other threads:[~2017-01-12 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 0:10 bug#25415: MySQL "server has gone away" when reloading database dump due to "max_allowed_packet" default Ben Sturmfels
2017-01-12 14:22 ` Ludovic Courtès [this message]
2017-01-12 23:29 ` Ben Sturmfels
2017-01-13 8:03 ` Ludovic Courtès
2021-09-14 11:51 ` zimoun
2021-10-12 21:42 ` zimoun
2021-11-26 1:51 ` zimoun
2022-01-04 23:00 ` zimoun
2022-06-23 9:54 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpe02w9c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25415@debbugs.gnu.org \
--cc=ben@stumbles.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).