Avoid temporary table updates being written to binlog if no data was altered

Given a slave server with read_only = on and binlog_format = statement which is used to perform complex queries involving some temporary table (which work as expected despite read_only mode)

However, even if no other data has (and could have) been altered on the slave, all statements dealing with the temporary table appear in the slave's binlog. It doesn't help to cover them in a transaction which is rolled back afterwards.

In contrast, with binlog_format = row nothing is written to the binlog as expected. But on a read-only slave the binlog format shouldn't matter, especially since "statement" is the default.

(Side note: the binlog record increases the GTID sequence number which might lead to issues when GTID strict mode is turned on).