From 33c27caeb5f5625c4e4799f710f53ad2236119a3 Mon Sep 17 00:00:00 2001
From: "paul@teton.kitebird.com" <>
Date: Mon, 7 Oct 2002 09:53:17 -0500
Subject: manual.texi	Document IO_THREAD and SQL_THREAD for SLAVE
 START/STOP.

---
 Docs/manual.texi | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/Docs/manual.texi b/Docs/manual.texi
index ba3e3c3a61b..87f6768fa77 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -24321,10 +24321,16 @@ summary of commands:
 @item @strong{Command} @tab @strong{Description}
 
 @item @code{SLAVE START}
- @tab Starts the slave thread. (Slave)
+ @tab Starts the slave thread.
+As of MySQL 4.0.2, you can add @code{IO_THREAD} or @code{SQL_THREAD}
+options to the statement to start the I/O thread or the SQL thread.
+The I/O thread reads queries from the master server and stores them in the
+relay log.  The SQL thread reads the relay log and executes the queries.
+(Slave)
 
 @item @code{SLAVE STOP}
- @tab Stops the slave thread. (Slave)
+ @tab Stops the slave thread. Like @code{SLAVE START}, this statement
+may be used with @code{IO_THREAD} and @code{SQL_THREAD} options. (Slave)
 
 @item @code{SET SQL_LOG_BIN=0}
 @tab Disables update logging if the user has the @code{SUPER} privilege.
-- 
cgit v1.2.1