Bug #80705 Mysqlpump in default configuration does not work
Submitted: 11 Mar 2016 14:50 Modified: 12 Mar 2016 5:38
Reporter: Morgan Tocker Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: mysqlpump Command-line Client Severity:S3 (Non-critical)
Version:5.7.11 OS:Any
Assigned to: CPU Architecture:Any

[11 Mar 2016 14:50] Morgan Tocker
The default usage of mysqlpump should be a complete backup when no arguments are provided.  It should then restore without errors.

How to repeat:
[root@mysqldb4 ~]# mysqlpump > mysqld4.sql
Dump progress: 0/1 tables, 2/2 rows
Dump completed in 846 milliseconds
[root@mysqldb4 ~]# mysql < mysqld4.sql
ERROR 1050 (42S01) at line 14: Table 'engine_cost' already exists

Then if I edit and remove engine_costs:

ERROR 1050 (42S01) at line 14: Table 'func' already exists

.. and so it continues.

Suggested fix:
- Do not dump any of the tables in mysql.* - they will always already exist.
- The data should be captured using replace statements (where it needs to be captured).

- Do not dump the help tables, or the help tables data.
[11 Mar 2016 14:54] Morgan Tocker
- Do not dump innodb_index_stats or innodb_table_stats (these are implied to be regenerated)
[12 Mar 2016 5:38] Umesh Shastry
Hello Morgan,

Thank you for the report.
Observed this issue with 5.7.11 build.