PDF (A4) - 41.5Mb
Man Pages (TGZ) - 272.3Kb
Man Pages (Zip) - 378.3Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb
SHOW BINLOG EVENTS [IN 'log_name'] [FROMpos] [LIMIT [offset,]row_count] Shows the events in the binary log. If you do not specify', the first binary log is displayed.log_name'SHOW BINLOG EVENTS requires theREPLICATION SLAVE privilege.
TheLIMIT clause has the same syntax as for theSELECT statement. SeeSection 15.2.13, “SELECT Statement”.
Issuing aSHOW BINLOG EVENTS with noLIMIT 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 toSHOW BINLOG EVENTS, use themysqlbinlog utility to save the binary log to a text file for later examination and analysis. SeeSection 6.6.9, “mysqlbinlog — Utility for Processing Binary Log Files”.
SHOW BINLOG EVENTS displays the following fields for each event in the binary log:
Log_nameThe name of the file that is being listed.
PosThe position at which the event occurs.
Event_typeAn identifier that describes the event type.
Server_idThe server ID of the server on which the event originated.
End_log_posThe position at which the next event begins, which is equal to
Posplus the size of the event.InfoMore detailed information about the event type. The format of this information depends on the event type.
For compressed transaction payloads, theTransaction_payload_event is first printed as a single unit, then it is unpacked and each event inside it is printed.
Some events relating to the setting of user and system variables are not included in the output fromSHOW BINLOG EVENTS. To get complete coverage of events within a binary log, usemysqlbinlog.
SHOW BINLOG EVENTS doesnot work with relay log files. You can useSHOW RELAYLOG EVENTS for this purpose.
PDF (A4) - 41.5Mb
Man Pages (TGZ) - 272.3Kb
Man Pages (Zip) - 378.3Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb