Return to Answer

• Jan 22, 2012 : MySql shell command not replicated to slave
• Apr 18, 2013 : Loading data in mysql using LOAD DATA INFILE, replication safe?
• May 04, 2014 : MySQL 5.6 showing wrong "second_behind_master"

• Jan 22, 2012 : MySql shell command not replicated to slave
• Apr 18, 2013 : Loading data in mysql using LOAD DATA INFILE, replication safe?
• May 04, 2014 : MySQL 5.6 showing wrong "second_behind_master"

Let me make a clarification. Personally, I do not like binlog_format ROW because of how bloated binary and relay logs become. In this post, I said use STATEMENT. That's just my preference. The more correct for me to say is : make the Master and its Slaves have the exact same binlog_format. Just make everything MIXED. You will have to bite the bullet and resync the Slave from scratch.

Let me make a clarification. Personally, I do not like binlog_format ROW because of how bloated binary and relay logs become. In this post, I said use STATEMENT. That's just my preference. The more correct for me to say is : make the Master and its Slaves have the exact same binlog_format. Just make everything MIXED. You will have to bite the bullet and resync the Slave from scratch.

#UPDATE 2014-09-08 08:06 EDT

Let me make a clarification. Personally, I do not like binlog_format ROW because of how bloated binary and relay logs become. In this post, I said use STATEMENT. That's just my preference. The more correct for me to say is : make the Master and its Slaves have the exact same binlog_format. Just make everything MIXED. You will have to bite the bullet and resync the Slave from scratch.