innodb stats tables

Bug #1431410 reported by Max Bubenick
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Data Dumper
Fix Released
High
Max Bubenick

Bug Description

Hi All,

I would like to know if it is a good idea to change the default behavior of mydumper or myloader to not dump/load mysql special tables like mysql.innodb_index_stats (eventually with an option --force-all-tables to avoid the filter).

This solution would avoid useless dumps, and avoid this kind of errors :

=============
** (myloader:24094): CRITICAL **: Error restoring mysql.innodb_index_stats from file mysql.innodb_index_stats.sql.gz: Duplicate entry 'dailysales-tSalesReportingConsult-PRIMARY-n_diff_pfx01' for key 'PRIMARY'

** (myloader:24094): CRITICAL **: Error restoring mysql.innodb_table_stats from file mysql.innodb_table_stats.sql.gz: Duplicate entry 'dailysales-tSalesReportingConsult' for key 'PRIMARY'
=============

I'm ready to make the patch myself and post it as a blueprint if you find that a good idea.

Please tell me your thought.

Related branches

Changed in mydumper:
milestone: none → 0.9.1
assignee: nobody → Max Bubenick (max-bubenick)
importance: Undecided → High
status: New → In Progress
Changed in mydumper:
status: In Progress → Fix Committed
Changed in mydumper:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.