Section 16.1.1.4 of the Reference Manual, (eg...
http://dev.mysql.com/doc/refman/5.0/en/replication-howto-masterstatus.html and
http://dev.mysql.com/doc/refman/5.6/en/replication-howto-masterstatus.html )
lists these steps for obtaining binary log coordinates on a prospective master in the course of setting up a new slave:
1. Execute FLUSH TABLES WITH READ LOCK
2. "In a different session on the master, use the SHOW MASTER STATUS statement to determine the current binary log file name and position..."
Why would it be necessary for the session in which SHOW MASTER STATUS is executed to not be the session in which FLUSH TABLES WITH READ LOCK has been executed?
http://dev.mysql.com/doc/refman/5.0/en/replication-howto-masterstatus.html and
http://dev.mysql.com/doc/refman/5.6/en/replication-howto-masterstatus.html )
lists these steps for obtaining binary log coordinates on a prospective master in the course of setting up a new slave:
1. Execute FLUSH TABLES WITH READ LOCK
2. "In a different session on the master, use the SHOW MASTER STATUS statement to determine the current binary log file name and position..."
Why would it be necessary for the session in which SHOW MASTER STATUS is executed to not be the session in which FLUSH TABLES WITH READ LOCK has been executed?