Re: drop table is written to bin-log, load table is NOT - why????

2005-01-27 Thread Lutz Maibach
Hello Artem, thanks for your answer. For selective replication I would check startup options --replicate-do-* and --replicate-wild-*. I'm using replicate-do-db on the client but the problem is, that the master sends the sql-statements of ALL databases to the repl-client and the

RE: drop table is written to bin-log, load table is NOT - why????

2005-01-27 Thread Artem Koltsov
Hello Lutz, I was not aware of this behavior of the master server. Maybe somebody with more insight can explain. If the traffic volume is so important I would turn on compression on the master-slave connection to reduce network traffic. I think it is slave_compressed_protocol=1 option in the

RE: drop table is written to bin-log, load table is NOT - why????

2005-01-26 Thread Artem Koltsov
Hello Lutz, As far as I know, binlog records only DML and DDL statements, and LOAD TABLE FROM MASTER is not the one. For selective replication I would check startup options --replicate-do-* and --replicate-wild-*. See http://dev.mysql.com/doc/mysql/en/replication-options.html for details. Also