May 22, 2012

Comment: Emulating global transaction ID with pt-heartbeat

… duplicate key errors for some time untill replication catches up.This should work fine in ‘row based replication‘ correct ? because even pointing to previous position and by ignoring duplicate key errors we are bringing the rows up to…

Comment: How to load large files safely into InnoDB with LOAD DATA INFILE

… you’re using different replication strategies. I can well imagine that row-based replication will indeed transfer the data, whereas statement-based might send the actual LOAD DATA INFILE command. There may even be differences based

Post: Percona Server 5.1.62-13.3 released!

… (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.62, including all the bug fixes… the changing names of the used databases in both Row-Based and Statement-Based replication. This was possible before by using tools like grep…

Post: Load management Techniques for MySQL

… be a good idea. It also often helps with monopolizing replication thread. For example if I need to delete old data…

Post: InnoDB's gap locks

… avoid phantom reads and to get a consistent Statement based replication. To accomplish that, row level locking databases also acquire gap locks. What… a consistent Statement based replication. If your application can deal with phantom reads and your binary log is in row format, changing the…

Post: Debugging problems with row based replication

… functions like RAND() are used in DML statements. A statement based replication slave can get out of sync with the master fairly… isn’t the case with row-based replication.  Only actual changes are written to the database with row-based logs.  Take as an… based binary log.  Since row-based logs only contain information about changed rows, a replication slave which does not find a row referenced in a row-based

Post: Can MySQL temporary tables be made safe for statement-based replication?

… not exist for row-based replication in MySQL 5.1 and later, but most installations I know of are using statement-based replication, even on… statement-based replication without some risk of breaking slaves. At some point I may test how it works with row-based replication; I believe even row-based

Post: Filtered MySQL Replication

… the master. Even though replicate-*-table options also have some issues they are much safer than database based counterparts. In some cases… wrote pretty good tutorial on creation for setting up BLACKHOLE Based Replication Filtering so I will not go into much of details… Replication can work pretty well for you. P.S It is in my todo to see how well MySQL 5.1 row based replication

Post: Statement based replication with Stored Functions, Triggers and Events

Statement based replication writes the queries that modify data in the Binary Log to replicate them on the slave or to use it…> create trigger Copy_data AFTER INSERT on t FOR EACH ROW INSERT INTO t_copy VALUE(NEW.i); mysql> insert into… are working with statement based replication. Knowing in advances how MySQL works internally can help us to improve our replication availability and data.

Post: STOP: DELETE IGNORE on Tables with Foreign Keys Can Break Replication

ROW* based replication. When using the latter, MySQL will log separate statements for each row that is deleted – so if the first 100 rows was… eventually replicated. [revin@forge rsandbox_5_5_170]$ ./master/use test … master [localhost] {msandbox} (test) > SELECT @@binlog_format; +—————–+ | @@binlog_format | +—————–+ | ROW | +—————–+ 1 row