Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
33c27cae
Commit
33c27cae
authored
Oct 07, 2002
by
paul@teton.kitebird.com
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi Document IO_THREAD and SQL_THREAD for SLAVE START/STOP.
parent
ff48c85c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
2 deletions
+8
-2
Docs/manual.texi
Docs/manual.texi
+8
-2
No files found.
Docs/manual.texi
View file @
33c27cae
...
...
@@ -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.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment