MySQL:Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEM
1:错误日志大量错误
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:原因:
查了下原因,tab_name 这个表上有2个唯一键。则使用INSERT … ON DUPLICATE KEY UPDATE ,且当前数据库binlog_format是statement格式,这种sql语句就会报unsafe。
官方手册:
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.
解决方法:
把binlog_format设置为ROW或者STATEMENT或者修改SQL。
一般情况下就是mysql配置问题,大家可以参考这篇文章:
推荐阅读
-
MySQL:Unsafe statement written to the binary log using statement format since BI
-
MySQL:Unsafe statement written to the binary log using statement format since BI
-
MySQL:Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEM
-
MySQL:Unsafe statement written to the binary log using statement format since BI
-
MySQL:Unsafe statement written to the binary log using statement format since BI
-
MySQL:Unsafe statement written to the binary log using statement format since BI
-
MySQL:Unsafe statement written to the binary log using state_MySQL
-
MySQL:Unsafe statement written to the binary log using state_MySQL
-
MySQL:Unsafe statement written to the binary log using statement format since BI