Re: Mysql 5.5.54 upgrade / Warnings

Am 30.06.2017 um 16:49 schrieb Pascal Longrais:
> Hello,
> 
> Since I upgraded mysql in use with DBMail 2.2.17, I now have 
> continuously warning messages flooding the log file.
> 
> 170630 16:30:25 [Warning] Unsafe statement written to the binary log 
> using statement format since BINLOG_FORMAT = STATEMENT. Statements 
> writing to a table with an auto-increment column after selecting from 
> another table are unsafe because the order in which rows are retrieved 
> determines what (if any) rows will be written. This order cannot be 
> predicted and may differ on master and the slave. Statement: INSERT INTO 
> dbmail_messages (mailbox_idnr,physmessage_id, seen_flag, answered_flag, 
> deleted_flag, flagged_flag, recent_flag, draft_flag, unique_id, status) 
> SELECT 1, physmessage_id, seen_flag, answered_flag, deleted_flag, 
> flagged_flag, recent_flag, draft_flag, 
> '00e88ea75a58a5653ab2fb0615e2bec6', status FROM dbmail_messages WHERE 
> message_idnr = 1179279
> 
> How is this warning critical?

no idea how should one esxplain it better than the message

> Can I fix something?
binlog-format = ROW

https://dev.mysql.com/doc/refman/5.7/en/binary-log-setting.html