MySQL 5.5 Reference Manual :: 12 SQL Statement Syntax :: 12.4 Database Administration Statements :: 12.4.5 SHOW Syntax :: 12.4.5.33 SHOW RELAYLOG EVENTS Syntax
Section Navigation [Toggle]
- 12.4.5 SHOW Syntax
- 12.4.5.1 SHOW AUTHORS Syntax
- 12.4.5.2 SHOW BINARY LOGS Syntax
- 12.4.5.3 SHOW BINLOG EVENTS Syntax
- 12.4.5.4 SHOW CHARACTER SET Syntax
- 12.4.5.5 SHOW COLLATION Syntax
- 12.4.5.6 SHOW COLUMNS Syntax
- 12.4.5.7 SHOW CONTRIBUTORS Syntax
- 12.4.5.8 SHOW CREATE DATABASE Syntax
- 12.4.5.9 SHOW CREATE EVENT Syntax
- 12.4.5.10 SHOW CREATE FUNCTION Syntax
- 12.4.5.11 SHOW CREATE PROCEDURE Syntax
- 12.4.5.12 SHOW CREATE TABLE Syntax
- 12.4.5.13 SHOW CREATE TRIGGER Syntax
- 12.4.5.14 SHOW CREATE VIEW Syntax
- 12.4.5.15 SHOW DATABASES Syntax
- 12.4.5.16 SHOW ENGINE Syntax
- 12.4.5.17 SHOW ENGINES Syntax
- 12.4.5.18 SHOW ERRORS Syntax
- 12.4.5.19 SHOW EVENTS Syntax
- 12.4.5.20 SHOW FUNCTION CODE Syntax
- 12.4.5.21 SHOW FUNCTION STATUS Syntax
- 12.4.5.22 SHOW GRANTS Syntax
- 12.4.5.23 SHOW INDEX Syntax
- 12.4.5.24 SHOW MASTER STATUS Syntax
- 12.4.5.25 SHOW OPEN TABLES Syntax
- 12.4.5.26 SHOW PLUGINS Syntax
- 12.4.5.27 SHOW PRIVILEGES Syntax
- 12.4.5.28 SHOW PROCEDURE CODE Syntax
- 12.4.5.29 SHOW PROCEDURE STATUS Syntax
- 12.4.5.30 SHOW PROCESSLIST Syntax
- 12.4.5.31 SHOW PROFILE Syntax
- 12.4.5.32 SHOW PROFILES Syntax
- 12.4.5.33 SHOW RELAYLOG EVENTS Syntax
- 12.4.5.34 SHOW SLAVE HOSTS Syntax
- 12.4.5.35 SHOW SLAVE STATUS Syntax
- 12.4.5.36 SHOW STATUS Syntax
- 12.4.5.37 SHOW TABLE STATUS Syntax
- 12.4.5.38 SHOW TABLES Syntax
- 12.4.5.39 SHOW TRIGGERS Syntax
- 12.4.5.40 SHOW VARIABLES Syntax
- 12.4.5.41 SHOW WARNINGS Syntax
SHOW RELAYLOG EVENTS [IN 'log_name'] [FROMpos] [LIMIT [offset,]row_count]
Shows the events in the relay log of a replication slave. If you
do not specify
', the
first relay log is displayed. This statement has no effect on
the master.
log_name'
The LIMIT clause has the same syntax as for
the SELECT statement. See
Section 12.2.9, “SELECT Syntax”.
Note
Issuing a SHOW RELAYLOG EVENTS
with no LIMIT clause could start a very
time- and resource-consuming process because the server
returns to the client the complete contents of the relay log
(including all statements modifying data that have been
received by the slave).
User Comments
Add your own comment.