List:General Discussion« Previous MessageNext Message »
From:Egor Egorov Date:March 23 2004 8:52pm
Subject:Re: --replicate* question
View as plain text  
Chua Choon Keng <choonkeng@stripped> wrote:
> Dear all, 
> 
> I am new to mysql replication. I know how to use
> the --replicate* options but I would like to know
> whether the options act as filter on the master or
> on the slave...

On the slave.

> 
> From the documentation, it says:
> "The --replicate-* rules are evaluated as follows
> to determine whether a statement will be executed
> by the slave or ignored"
> 
> This gives me the impression that all update
> queries are sent to slave, but if they are not
> matched by the rules, they are ignored. In my case,
> I am replicating a database with infrequent
> updates, but they are many other databases on the
> master with frequent updates etc. If my guess is
> correct, then I am wasting a lot of bandwidth as my
> master & slave are world apart...
> 

What about using binlog-do-db=database_name option? In this case only updates will be
logged if the current database is database_name:
	http://www.mysql.com/doc/en/Binary_log.html



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   Egor.Egorov@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
       <___/   www.mysql.com



Thread
--replicate* questionChua Choon Keng23 Mar
  • Re: --replicate* questionEgor Egorov23 Mar
Re: --replicate* questionChua Choon Keng24 Mar
  • Re: --replicate* questionEgor Egorov24 Mar
    • Re: --replicate* questionEgor Egorov24 Mar