MySQL Manual
4 Database Administration
- 4.10 Replication in MySQL
- 4.10.1 Introduction
- 4.10.2 Replication Implementation Overview
- 4.10.3 Replication Implementation Details
- 4.10.4 How To Set Up Replication
- 4.10.5 Replication Features and Known Problems
- 4.10.6 Replication Options in `my.cnf'
- 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.8 Replication FAQ
- 4.10.9 Troubleshooting Replication
4.10.7 SQL Commands Related to Replication
Replication can be controlled through the SQL interface. Here is the summary of commands. Near each command you will find ``(Slave)'', meaning this command is issued on the slave, or ``Master'', meaning it is issued on the master.
Subsections
- 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)
User Comments
| Posted by dpk on Tuesday July 23 2002, @10:03am | [Delete] [Edit] |
SQL_LOG_BIN = 0 doesn't work in 3.23.51 - binary
logs continue. Also, the docs on this page only
apply to 4.0.2. There is no SUPER privilege for
3.anything from what I can tell. The privilege for
3.23.x is supposedly PROCESS - but that doesn't
work either.
| Posted by ilya on Friday May 17 2002, @6:24am | [Delete] [Edit] |
MySQL ver 3.23.41:
command "SET SQL_LOG_BIN=0" and the subsequent
INSERT DELAYED ... result in the insert going
to the binary log. Are there any work arounds?
| Posted by Herve Galligani on Wednesday November 6 2002, @11:50am | [Delete] [Edit] |
SET GLOBAL SQL_SLAVE_SKIP_COUNTER=n doesn't
work but SET SQL_SLAVE_SKIP_COUNTER=n works
| Posted by Massimo Ferrario on Wednesday February 26 2003, @8:14am | [Delete] [Edit] |
SHOW BINLOG EVENTS is not working in version 3.23.54-log
mysql> SHOW BINLOG EVENTS;
ERROR 1064: You have an error in your SQL syntax near 'binlog events' at line 1
Is it a 4.0 feature?
| Posted by Unreal H on Tuesday March 18 2003, @2:09am | [Delete] [Edit] |
'LOAD TABLE tblname FROM MASTER' must need the tables or the databases SELECT privileges in master
