Reading more of the code, I realize now that --safe-slave-backup actually does what I want. I can then use it with or without --no-lock as I prefer.
The original reason for creating --safe-slave-backup is something else, so I didn't realize that it actually does a stop slave sql_thread, exactly as I want.
Reading more of the code, I realize now that --safe-slave-backup actually does what I want. I can then use it with or without --no-lock as I prefer.
The original reason for creating --safe-slave-backup is something else, so I didn't realize that it actually does a stop slave sql_thread, exactly as I want.
I will close this bug then.