Common parameters:--start-datetime=datetime starts reading from the binary log of events that are equal to or later than the DateTime parameter in the 1th date time. The datetime value is relative to the local time zone on the machine that is running Mysqlbinlog. The value format should conform to the datetime or timestamp data type. --stop-datetime=datetime stops reading from the binary log for events that are equal to or later than the DateTime parameter in the 1th date time. See the--start-datetime option for a description of the datetime value. This option can help you recover in a timely manner. The--start-position=n starts reading from the event that the 1th position in the binary log equals N parameter. --stop-position=n stops reading from the event that the 1th position in the binary log is equal to and greater than the N parameter. --base64-output=decode-rows will show the SQL change from row mode-D is the same as the--database effect, specifying a database name. --offset=n,-o N skips the first n entries. Note: 1. Do not view the Binlog file that is currently being written to 2. Do not add--force parameter to force access 3. If Binlog format is line mode, add-VV parameter based on start/end time Mysqlbinlog--start-datetime= ' 2018-07-10 00:00:00 '--stop-datetime= ' 2018-07-10 01:01:01 '-d library name binary file based on POS value Mysqlbinlog--start-position=107-- STOP-POSITION=1000-D Library name binary file converted to readable text mysqlbinlog-–base64-output=decode-rows-vv-d Library name binary file
The Mysqlbinlog command uses