Improving replication reliability with MIXED binlog_format and temporary tables

binlog_format set to MIXED and temporary tables can break replication, in MariaDB and MySQL versions prior to 8.0.

To avoid replication issues when binlog_format is set to MIXED, slave servers must be restarted using the approach outlined in MySQL 5.7 documentation MySQL5.7Docs: stop SQL apply, monitor usage of temporary tables and restart only when there are no temporary tables on the slave, otherwise replication will break.

MySQL 8.0 fixed this issue MySQL8.0docs, by changing the behaviour of MIXED logging. MIXED logging was changed to switch to ROW logging when temporary tables are used, eliminating replication of temporary tables and possible replication issues.

Given that binlog_format defaults to MIXED since 10.2.4, inclusion of this feature will make replication more resilient with the default settings, improving the user experience.