SHOW BINLOG EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count]
Shows the events in the binary log. If you do not specify
first binary log is displayed.
EVENTS requires the
LIMIT clause has the same syntax as for
SELECT statement. See
Section 13.2.13, “SELECT Statement”.
SHOW BINLOG EVENTS
LIMIT clause could start a very
time- and resource-consuming process because the server
returns to the client the complete contents of the binary log
(which includes all statements executed by the server that
modify data). As an alternative to
BINLOG EVENTS, use the
mysqlbinlog utility to save the binary log
to a text file for later examination and analysis. See
Section 4.6.9, “mysqlbinlog — Utility for Processing Binary Log Files”.
SHOW BINLOG EVENTS displays the
following fields for each event in the binary log:
The name of the file that is being listed.
The position at which the event occurs.
An identifier that describes the event type.
The server ID of the server on which the event originated.
The position at which the next event begins, which is equal to
Posplus the size of the event.
More detailed information about the event type. The format of this information depends on the event type.
For compressed transaction payloads, the
Transaction_payload_event is first printed as
a single unit, then it is unpacked and each event inside it is
Some events relating to the setting of user and system variables
are not included in the output from
BINLOG EVENTS. To get complete coverage of events
within a binary log, use mysqlbinlog.
SHOW BINLOG EVENTS does
not work with relay log files. You can use
SHOW RELAYLOG EVENTS for this