mysql binlog

該格式描述事件時binlog version 4中為了取代之前版本的START_EVENT_3事件而引入的。是binlog文件的第一個事件，並在一個binlog文件中僅出現一次。具體定義：

binlog-version：binlog版本
mysql-server version：服務器版本
create timestamp：指明binlog文件的創建時間。如果該binlog是由於切換產生，那麽該字段是0
event header length：189
event type header lengths：記錄所有事件的私有事件頭的長度，event的個數定義5.6，5.7為40個，也就是40個字節

[mysql26@localhost data]$ hexdump -Cv mysql-bin.000002 > 2.txt  
[mysql26@localhost data]$ vi 2.txt  

00000000  fe 62 69 6e 46 c4 a4 5a  0f 0b 00 00 00 74 00 00  |.binF..Z.....t..|  
00000010  00 78 00 00 00 01 00 04  00 35 2e 36 2e 32 36 2d  |.x.......5.6.26-|  
00000020  64 65 62 75 67 2d 6c 6f  67 00 00 00 00 00 00 00  |debug-log.......|  
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|  
00000040  00 00 00 00 00 00 00 00  00 00 00 46 c4 a4 5a 13  |...........F..Z.|  
00000050  38 0d 00 08 00 12 00 04  04 04 04 12 00 00 5c 00  |8.............\.|  
00000060  04 1a 08 00 00 00 08 08  08 02 00 00 00 0a 0a 0a  |................|  
00000070  19 19 00 01 c8 a1 c5 19  62 c4 a4 5a 02 0b 00 00  |........b..Z....|  
00000080  00 47 00 00 00 bf 00 00  00 08 00 01 00 00 00 00  |.G..............|  
00000090  00 00 00 03 00 00 1a 00  00 00 00 00 00 01 00 00  |................|  
000000a0  00 40 00 00 00 00 06 03  73 74 64 04 21 00 21 00  |[email protected].!.!.|  
000000b0  21 00 79 7a 73 00 42 45  47 49 4e 30 85 8c ba 62  |!.yzs.BEGIN0...b|  
000000c0  c4 a4 5a 13 0b 00 00 00  2d 00 00 00 ec 00 00 00  |..Z.....-.......|  
000000d0  00 00 46 00 00 00 00 00  01 00 03 79 7a 73 00 02  |..F........yzs..|  
 

分析：

1、開頭4個字節binlog magic number：fe 62 69 6e，即.bin

2、第一個binlog事件是FORMAT_DESCRIPTION_EVENT。

3、timestamp： 46 c4 a4 5a，即小端顯示0x5aa4c446，十進制1520747590，
[mysql26@localhost data]$ date -d "@1520747590"
Sat Mar 10 21:53:10 PST 2018

binlog解析的時間是：#180310 21:53:10 server id 11 end_log_pos 120 CRC32 0x19c5a1c8 Start: binlog v 4, server v 5.6.26-debug-log created 180310 21:53:10 at startup

3、event type：0f，即15

5、server-id：0b 00 00 00，即小端顯示0x00 00 00 0b，即為11

6、event size：74 00 00 00：0x 00 00 00 74，116。120-4（.bin）

7、next-log pos：78 00 00 00：0x00 00 00 78，120，下一個event的位置，相對文件頭位置，和end_log_pos 120一致

8、flag：01 00；為0X0001那麽會在MYSQLBINLOG輸出中報一個警告說本binlog沒有關閉

9、binlog version：04 00，小端顯示及0X0004,和mysqlbinlog中的解析Start: binlog v 4一致

10、mysql server version：5.6.26-debug-log，剩下的字節0填充

00000010                              35 2e 36 2e 32 36 2d  |.x.......5.6.26-|  
00000020  64 65 62 75 67 2d 6c 6f  67 00 00 00 00 00 00 00  |debug-log.......|  
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|  
00000040  00 00 00 00 00 00 00 00  00 00 00   

11、create stamp：46 c4 a4 5a，和event頭一樣

12、event header length：13，即19字節

13、event header lengths：array[30]-[32]:0a 0a 0a，表示 WRITE_ROWS_EVENT = 30,UPDATE_ROWS_EVENT = 31, DELETE_ROWS_EVENT = 32的私有事件頭長度

00000050  38 0d 00 08 00 12 00 04  04 04 04 12 00 00 5c 00  |8.............\.|  
00000060  04 1a 08 00 00 00 08 08  08 02 00 00 00 0a 0a 0a  |................|  
00000070  19 19 00 01 c8 a1 c5 19  

參考：http://blog.itpub.net/7728585/viewspace-2133189/

解析MySQL binlog --（2）FORMAT_DESCRIPTION_EVENT