MySQL Error: Unsafe statement written to the binary log using statement format

[onallion]

Hello,

I've been seeing the following errors in my MySQL (MariaDB 10.1) error log:

[Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: delete from history_log where itemid=25639 limit 5000

It goes on like this for a while and then it suppresses the warning temporarily:

[Note] Suppressing warnings of type 'The statement is unsafe because it uses a LIMIT                              clause. This is unsafe because the set of rows included cannot be predicted.' for up to 300 seconds because of flooding.

I am currently only monitoring one host (the server itself) and haven't noticed any issues, but having these errors is making me uncomfortable. Has anyone encountered this before and have any advice for me?

[batchenr]

it seems that something making unsafe statements at your mariadb

see ref :

https://mariadb.com/kb/en/mariadb/unsafe-statements-for-replication/

it seems like it have a solution-
look here:

https://www.psce.com/blog/2012/04/17/why-a-statement-can-be-unsafe-when-it-uses-limit-clause/

hope it helps

[onallion]

I see.

I will try to change the binlog to "mixed" format and update. Thank you

[cesarsj]

Did you change binlog to "mixed"? Did you had any problem since changed? Because I am thinking on make this change too.