When setting up master/slave replication in Mysql, do you then need to ignore any tables in /etc/mysql/my.cnf or should replicate_wild_ignore_table be leaved out under normal circumstances?

This is what I'm doing...


replicate_wild_ignore_table = mysql.%,information_schema.%,phpmyadmin.%

2 Answers 2


Please change the directive to one of the following:




mysql database

No need to do mysql. Why? Doing GRANT and REVOKE commands will bypass replicate_wild_ignore_table=mysql.% because the SQL does not explicitly mention mysql schema tables.

This will get by replicate_wild_ignore_table=mysql.%:

GRANT ALL PRIVILEGES ON *.* to rolando@locahost;

This will get caught by replicate_wild_ignore_table=mysql.%:

INSERT INTO mysql.user VALUES (...);

If you want to keep replicate_wild_ignore_table=mysql.%, I suggest the following:

SET sql_log_bin = 0; INSERT INTO mysql.user VALUES (...);

This will prevent the SQL from being recorded in the master's binary logs. Consequently, all SQL executed in the DB Session after SET sql_log_bin = 0; will not replicate.

information_schema database

As far as the information_schema database, mysqld uses it to monitor database metadata. Each is unique to the MySQL instance. They never replicate intrinsically because you have the option to keep different table on Master and Slave. If the information_schema was replicated, then creating replication schemes such as

would be impossible for Slaves to handle.






should be all you need. Notwithstanding, make sure any SQL that prepends phpmyadmin to all it table names may still slide by if the default database is not phpmyadmin.

  • '@Rolando: If I want to keep different permissions on my slave and to achieve it If I use replicate_wild_ignore_table=mysql.user (same for other tables related with permissions like db, table_priv and column_priv) then it is okay or any issue....not preventing whole db as mysql also keep stored routines which should be replicate....I will be very thankful if you clear it.... Commented May 18, 2016 at 6:15

I think it all depends on why you are replicating. If you want a strict 1:1 copy of your db server then you don't need any ignore_table entries. If you just want to make some subset of your DBs/tables available then you will need to add entries to filter them in/out.

But as you pointed out in the included link - this creates a risk of inadvertently breaking replication. Since every binlog statement gets copied and run on the replication slave if it encounters a reference that hasn't been specifically dealt with and the referred table isn't available it will error out. Fixing this is usually trivial but it does require attention.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.