This article mainly introduces MySQL: UnsafestatementwrittentothebinarylogusingstatementformatsinceBINLOG_FORMATSTATEM. For more information, see
1: a large number of error logs
150602 14:40:02 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... SELECT... on duplicate key update is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. this order cannot be predicted and may differ on master and the slave. statement: insert into tab_name
2: cause:
Check the cause. the tab_name table has two unique keys. INSERT... On duplicate key update, and the current database binlog_format is in statement format, this SQL statement will report unsafe.
Official Manual:
INSERT... On duplicate key update statements on tables with multiple primary or unique keys. when executed against a table that contains more than one primary or unique key, this statement is considered unsafe, being sensitive to the order in which the storage engine checks the keys, which is not deterministic, and on which the choice of rows updated by the MySQL Server depends.
Solution:
Set binlog_format to ROW or STATEMENT or modify SQL.
Under normal circumstances is mysql configuration problem, you can refer to this article: http://www.bitsCN.com/article/84357.htm