content_image/836526.jpg
the group_replication_applier  or group_replication_recovery channels. 

To specify more than one database to ignore, use this option multiple times, once for each database. Because database names can contain commas, if you supply a comma-separated list, it is treated as the name of a single database. 

As with --replicate-do-db , the precise effect of this filtering depends on whether statement-based or row-based replication is in use, and are described in the next several paragraphs. 

Statement-based replication.  Tells the replication SQL thread not to replicate any statement where the default database (that is, the one selected by USE ) is db_name . 

Row-based replication.  Tells the replication SQL thread not to update any tables in the database db_name . The default database has no effect. 

When using statement-based replication, the following example does not work as you might expect. Suppose that the replica is started with --replicate-ignore-db=sales  and you issue the following statements on the source: 

USE prices; UPDATE sales.january SET amount=amount+1000; 

The UPDATE  statement is  replicated in such a case because --replicate-ignore-db  applies only to the default database (determined by the USE  statement). Because the sales  database was specified explicitly in the statement, the statement has not been filtered. However, when using row- based replication, the UPDATE  statement’s effects are not  propagated to the replica, and the replica’s copy of the sales.january  table is unchanged; in this instance, --replicate-ignore-db=sales causes all  changes made to tables in the source’s copy of the sales  database to be ignored by the replica. 

You should not use this option if you are using cross-database updates and you do not want these updates to be replicated. See Section 17.2.5, “How Servers Evaluate Replication Filtering Rules” . 

If you need cross-database updates to work, use --replicate-wild-ignore-table= db_name .% instead. See Section 17.2.5, “How Servers Evaluate Replication Filtering Rules” . 

• --replicate-do-table= db_name.tbl_name 

Note 

This option affects replication in the same manner that --binlog-ignore- db  affects binary logging, and the effects of the replication format on how -- replicate-ignore-db  affects replication behavior are the same as those of the logging format on the behavior of --binlog-ignore-db . 

This option has no effect on BEGIN , COMMIT , or ROLLBACK  statements. 

<img src='content_image/836526.jpg'>

Creates a replication filter by telling the replication SQL thread to restrict replication to a given table. To specify more than one table, use this option multiple times, once for each table. This works for both cross-database updates and default database updates, in contrast to --replicate-do-db . See 

