Comment 2 for bug 1717158

Yeah, the loop with CREATE TEMPORARY...; INSERT...SELECT; DROP TEMPORARY was an example to show the effect; I reckon it would be impossible to make --safe-slave-backup work in such case. Guess the best alternative (better than waiting for position to advance) is to inspect binlog and find the DROP TEMPORARY, stop immediately after and check... This would be the ultimate fix, as it only makes sense to check open_slave_temp_tables again after a DROP TEMPORARY.