3 ms·

Note that with 5.7 there is a new tool, "mysqlpump" that can do parallel export/import and direct compression. I haven't test it yet because mysqldump is enoug

• pizza234 9y ago
  mysqlpump is a terrible product, both in the implementation and the design, in particular: - it will create broken backups for databases with triggers; the bug has been open for more than an year; - it breaks compatibility with the `mysqldump` output format, since it adds the database name to the table names (without the option to avoid this); - it has an unclear product placement: it's not a subset of mysqldump (it has functionalities added), but it's not a superset either (it has functionalities missing). The status of the mysql dump/restore tools is, in general, very underwhelming. The Percona mysqldump version adds a switch for improving innodb indexes re-creation on restore (by moving the ADD KEY after the records insertion), but it's never been merged upstream. Also, the pattern table matches is extremely useful for cases where it's required, but it's not clear why they added it to mysqlpump rather than to mysqldump. Mysqlimport has a limitation (bug?) which prevents tables with mixed UTF-8 data and JSON columns to be imported (!!).