Comments on: What are your favorite MySQL replication filtering rules?

By: Xaprb

Xaprb — Sun, 21 Oct 2007 19:33:00 +0000

Good suggestions, thanks. I’m pretty sure the elapsed-time and user-variable problems are solved by meta-data added to the binlog events, but I’ll check.

An interesting question: do user-variables cause issues like temp tables in case the slave crashes and restarts? I think they don’t but I’m not sure. I’ll check that too.

By: Sheeri

Sheeri — Sun, 21 Oct 2007 19:29:30 +0000

Well, one trick is when you’re replicating only one database but want to use another without having to change replication, do everything using dot notation from the allowed db.

ie,

use alloweddb;
INSERT INTO different.tbl1 (col1, col2, col3) VALUES (val1,val2,val3);

But that’s of course a huge hack.

One thing that’s interesting that came up as a question at work the other day — if you do the following:

BEGIN;
INSERT INTO TimeTbl (beginTime) SELECT NOW();
— some long query here
INSERT INTO TimeTbl (endTime) SELECT NOW();
COMMIT;

does it replicate properly? I’d like to see things like highlighting where replication falls apart (like with SET statements, user variables, etc….and maybe how one can get around those).

By: Xaprb

Xaprb — Sun, 21 Oct 2007 13:22:46 +0000

Ethan, do you mean timezones as they relate to replication, or just timezones in general?

By: Ethan

Ethan — Sun, 21 Oct 2007 12:59:07 +0000

Yes, information on replication of permissions would be really useful.

Info about other config options in the mysql database (timezones etc) would also be helpful

By: Xaprb

Xaprb — Sun, 21 Oct 2007 12:30:32 +0000

Well, in a book about how to make replication work right, we should probably avoid this setting and concentrate on helping solve whatever’s creating the need for it :-)

By: Marc

Marc — Sun, 21 Oct 2007 01:36:35 +0000

–slave-skip-errors=all

I know most people don’t agree with this however.