- Documentation Library
- Table of Contents
- MySQL 5.5 Manual
- MySQL 5.4 Manual
- MySQL 5.1 Manual
- MySQL 5.0 Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
MySQL 3.23, 4.0, 4.1 Reference Manual :: 12 SQL Statement Syntax :: 12.5 Replication Statements :: 12.5.2 SQL Statements for Controlling Slave Servers :: 12.5.2.4 MASTER_POS_WAIT() Syntax
Section Navigation [Toggle]
- 12.5.2 SQL Statements for Controlling Slave Servers
- 12.5.2.1 CHANGE MASTER TO Syntax
- 12.5.2.2 LOAD DATA FROM MASTER Syntax
- 12.5.2.3 LOAD TABLE tbl_name FROM MASTER Syntax
- 12.5.2.4 MASTER_POS_WAIT() Syntax
- 12.5.2.5 RESET SLAVE Syntax
- 12.5.2.6 SET GLOBAL SQL_SLAVE_SKIP_COUNTER Syntax
- 12.5.2.7 START SLAVE Syntax
- 12.5.2.8 STOP SLAVE Syntax
SELECT MASTER_POS_WAIT('master_log_file', master_log_pos [, timeout])
This is actually a function, not a statement. It is used to ensure that the slave has read and executed events up to a given position in the master's binary log. See Section 11.10.4, “Miscellaneous Functions”, for a full description.
User Comments
NOTE: If you have a cyclical replication setup (ie. more then two servers in a replication chain) do *NOT* rely on 'SHOW MASTER STATUS' on the slave's MASTER for values to use in the master_pos_wait function. This is because if the slave had just finished executing a binlog event that didn't originally come from its own MASTER, the master_log_pos value to be used in this function won't work. I feel this is a bug, but it is apparently designed to work this way. Don't ask me why.
WARNING: does not block if slave errors.
If show slave status is reporting an error, function returns instantly.
Add your own comment.