Oracle 5.0 Reference Manual page 1152

START SLAVE [SQL_THREAD] UNTIL
MASTER_LOG_FILE = 'log_name', MASTER_LOG_POS =
START SLAVE [SQL_THREAD] UNTIL
RELAY_LOG_FILE = 'log_name', RELAY_LOG_POS =
thread_types:
[thread_type
thread_type: IO_THREAD | SQL_THREAD
START SLAVE
events from the master server and stores them in the relay log. The SQL thread reads events from the
relay log and executes them.
If
START SLAVE
in that case, it might be that the slave threads start and then later stop (for example, because they do
not manage to connect to the master or read its binary log, or some other problem).
does not warn you about this. You must check the slave's error log for error messages generated by
the slave threads, or check that they are running satisfactorily with
START SLAVE
have started. However, the I/O thread may not yet have connected. For this reason, a successful
START SLAVE
guarantee that
running and connected). For more information, see
and Section 16.1.3.1, "Checking Replication
You can add
start.
An clause may be added to specify that the slave should start and run until the SQL thread
UNTIL
reaches a given point in the master binary log or in the slave relay log. When the SQL thread reaches
that point, it stops. If the
thread. Otherwise, it starts both slave threads. If the SQL thread is running, the
ignored and a warning is issued.
For an
UNTIL
log options.
Any
UNTIL
that includes no
The
UNTIL
before the point where you want to avoid having the slave replicate an event. For example, if an unwise
DROP TABLE
up to that point but no farther. To find what the event is, use
or slave relay log, or by using a
If you are using
that you start the slave with the
running when the slave server starts. It is probably best to use this option in an option file rather than
on the command line, so that an unexpected server restart does not cause it to be forgotten.
The
SHOW SLAVE STATUS
condition.
UNTIL
In old versions of MySQL (before 4.0.5), this statement was called
accepted in MySQL 5.0 for backward compatibility, but is deprecated and is removed in MySQL 5.6.
13.4.2.8.
STOP SLAVE
SQL Statements for Controlling Slave Servers
[, thread_type] ... ]
with no
thread_type
START SLAVE
succeeds in starting the slave threads, it returns without any error. However, even
sends an acknowledgment to the user after both the I/O thread and the SQL thread
causes
SHOW SLAVE STATUS
Slave_IO_Running=Yes
and
IO_THREAD SQL_THREAD
SQL_THREAD
clause, you must specify both a log file name and position. Do not mix master and relay
condition is reset by a subsequent
clause, or a server restart.
UNTIL
clause can be useful for debugging replication, or to cause replication to proceed until just
statement was executed on the master, you can use
SHOW BINLOG EVENTS
to have the slave process replicated queries in sections, it is recommended
UNTIL
--skip-slave-start
statement includes output fields that display the current values of the
Syntax
log_pos
log_pos
options starts both of the slave threads. The I/O thread reads
requires the
SUPER
to show Slave_SQL_Running=Yes, but this does not
(because
Slave_IO_Running=Yes
Section 13.7.5.31,
Status".
options to the statement to name which of the threads to
option is specified in the statement, it starts only the SQL
statement, a
STOP SLAVE
mysqlbinlog
statement.
[1462]
1132
[578] privilege.
START SLAVE
SHOW SLAVE STATUS.
only if the I/O thread is
"SHOW SLAVE STATUS
UNTIL
START SLAVE
to tell the slave to execute
UNTIL
with the master binary log
option to prevent the SQL thread from
START. This usage is still
SLAVE
Syntax",
clause is
statement