MySQL Manual
4 Database Administration
- 4.10 Replication in MySQL
- 4.10.7 SQL Commands Related to Replication
- 4.10.7.1
START SLAVE(slave) - 4.10.7.2
STOP SLAVE(slave) - 4.10.7.3
SET SQL_LOG_BIN=0|1(master) - 4.10.7.4
SET GLOBAL SQL_SLAVE_SKIP_COUNTER=n(slave) - 4.10.7.5
RESET MASTER(master) - 4.10.7.6
RESET SLAVE(slave) - 4.10.7.7
LOAD TABLE tblname FROM MASTER(slave) - 4.10.7.8
LOAD DATA FROM MASTER(slave) - 4.10.7.9
CHANGE MASTER TO master_def_list(slave) - 4.10.7.10
MASTER_POS_WAIT()(slave) - 4.10.7.11
SHOW MASTER STATUS(master) - 4.10.7.12
SHOW SLAVE HOSTS(master) - 4.10.7.13
SHOW SLAVE STATUS(slave) - 4.10.7.14
SHOW MASTER LOGS(master) - 4.10.7.15
SHOW BINLOG EVENTS(master) - 4.10.7.16
PURGE MASTER LOGS(master)
- 4.10.7.1
4.10.7.16 PURGE MASTER LOGS (master)
PURGE MASTER|BINARY LOGS TO 'logname' ; PURGE MASTER|BINARY LOGS BEFORE 'date'
The BEFORE variant is available in MySQL 4.1; its date argument
can be in format 'YYYY-MM-DD HH:MI:SS'.
MASTER and BINARY are here synonyms.
Deletes all the
binary logs that are listed in the log
index as being strictly prior to the specified log or date, and
removes them from the
log index, so that the given log now becomes the first.
Example:
PURGE MASTER LOGS TO 'mysql-bin.010' ; PURGE MASTER LOGS BEFORE '2003-04-02 22:46:26' ;
This command will do nothing and fail with an error if you have an active slave that is currently reading one of the logs you are trying to delete. However, if you have a dormant slave, and happen to purge one of the logs it wants to read, the slave will be unable to replicate once it comes up. The command is safe to run while slaves are replicating -- you do not need to stop them.
You must first check all the slaves with SHOW SLAVE STATUS to
see which log they are on, then do a listing of the logs on the
master with SHOW MASTER LOGS, find the earliest log among all
the slaves (if all the slaves are up to date, this will be the
last log on the list), backup all the logs you are about to delete
(optional) and purge up to the target log.
