The Ultimate Guide to High Availability with MariaDB

Is `DELETE IGNORE` replication safe?

It's tempting to use `DELETE IGNORE` to prune rows from a table referenced by foreign keys.

https://www.percona.com/blog/stop-delete-ignore-on-tables-with-foreign-keys-can-break-replication/ advises that `DELETE IGNORE` is not safe when using `binlog-format = STATEMENT`, which makes sense.

It also makes sense that it should be safe with `binlog-format = ROW`.

But is it replication safe with `binlog-format = MIXED`?

In other words: How is `DELETE IGNORE` added to the binlog?

Answer Answered by Ian Gilfillan in this comment.

If the format is mixed, unsafe statements are logged using the row-based format, while safe statements use the statement-based format. See Unsafe Statements for Statement-based Replication.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.