enterprise-support team mailing list archive

[Max Bubenick <max.bubenick@xxxxxxxxxxx>]

Public bug reported:

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.

** Affects: mydumper
     Importance: High
     Assignee: Max Bubenick (max-bubenick)
         Status: In Progress

** Changed in: mydumper
    Milestone: None => 0.9.1

** Changed in: mydumper
     Assignee: (unassigned) => Max Bubenick (max-bubenick)

** Changed in: mydumper
   Importance: Undecided => High

** Changed in: mydumper
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1431410

Title:
  innodb stats tables

To manage notifications about this bug go to:
https://bugs.launchpad.net/mydumper/+bug/1431410/+subscriptions