前言
上一篇檔案MySql Binlog初識，對Binlog的引數，格式以及個別事件做了詳細介紹，但是Binlog事件數量比較多，上篇文章中沒有對所有事件進行介紹；本文將對Binlog的事件進行簡單說明，必要的時候通過SQL觸發相關的事件，以下基於Mysql5.5，5.0以前的版本不考慮。
Binlog事件
1.UNKNOWN_EVENT
此事件從不會被觸發，也不會被寫入binlog中；發生在當讀取binlog時，不能被識別其他任何事件，那被視為UNKNOWN_EVENT。
2.START_EVENT_V3
每個binlog檔案開始的時候寫入的事件，此事件被用在MySQL3.23 – 4.1，MYSQL5.0以後已經被FORMAT_DESCRIPTION_EVENT取代。
3.QUERY_EVENT
執行更新語句時會生成此事件，包括：create，insert，update，delete；
手動觸發：
|
1 2 3 4 5 |
insert into btest values(1,100,'zhaohui'); | bin-log.000001 | 432 | Query | 1 | 536 | use `test`; insert into btest values(1,100,'zhaohui') | | bin-log.000001 | 536 | Xid | 1 | 563 | COMMIT /* xid=30 */ |
4.STOP_EVENT
當mysqld停止時生成此事件
可以手動停止mysql，生成的事件：
|
1 |
| bin-log.000001 | 563 | Stop | 1 | 582 | |
5.ROTATE_EVENT
當mysqld切換到新的binlog檔案生成此事件，切換到新的binlog檔案可以通過執行flush logs命令或者binlog檔案大於max_binlog_size引數配置的大小；
手動觸發：
|
1 2 3 4 5 6 7 8 9 10 11 |
mysql> flush logs; Query OK, 0 rows affected (0.24 sec) mysql> show binlog events in 'bin-log.000002'; +----------------+-----+-------------+-----------+-------------+---------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+-----+-------------+-----------+-------------+---------------------------------------+ | bin-log.000002 | 4 | Format_desc | 1 | 107 | Server ver: 5.5.29-log, Binlog ver: 4 | | bin-log.000002 | 107 | Rotate | 1 | 148 | bin-log.000003;pos=4 | +----------------+-----+-------------+-----------+-------------+---------------------------------------+ |
6.INTVAR_EVENT
當sql語句中使用了AUTO_INCREMENT的欄位或者LAST_INSERT_ID()函式；此事件沒有被用在binlog_format為ROW模式的情況下。
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
insert into btest (age,name)values(100,'zhaohui'); mysql> show binlog events in 'bin-log.000003'; +----------------+-----+-------------+-----------+-------------+---------------------------------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+-----+-------------+-----------+-------------+---------------------------------------------------------------+ | bin-log.000003 | 4 | Format_desc | 1 | 107 | Server ver: 5.5.29-log, Binlog ver: 4 | | bin-log.000003 | 107 | Query | 1 | 175 | BEGIN | | bin-log.000003 | 175 | Intvar | 1 | 203 | INSERT_ID=2 | | bin-log.000003 | 203 | Query | 1 | 315 | use `test`; insert into btest (age,name)values(100,'zhaohui') | | bin-log.000003 | 315 | Xid | 1 | 342 | COMMIT /* xid=32 */ | +----------------+-----+-------------+-----------+-------------+---------------------------------------------------------------+ 5 rows in set (0.00 sec) |
btest表中的id為AUTO_INCREMENT，所以產生了INTVAR_EVENT
7.LOAD_EVENT
執行LOAD DATA INFILE 語句時產生此事件，在MySQL 3.23版本中使用；
8.SLAVE_EVENT
未使用的
9.CREATE_FILE_EVENT
執行LOAD DATA INFILE 語句時產生此事件，在MySQL4.0和4.1版本中使用；
10.APPEND_BLOCK_EVENT
執行LOAD DATA INFILE 語句時產生此事件，在MySQL4.0版本中使用；
11.EXEC_LOAD_EVENT
執行LOAD DATA INFILE 語句時產生此事件，在MySQL4.0和4.1版本中使用；
12.DELETE_FILE_EVENT
執行LOAD DATA INFILE 語句時產生此事件，在MySQL4.0版本中使用；
13.NEW_LOAD_EVENT
執行LOAD DATA INFILE 語句時產生此事件，在MySQL4.0和4.1版本中使用；
14.RAND_EVENT
執行包含RAND()函式的語句產生此事件，此事件沒有被用在binlog_format為ROW模式的情況下；
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
mysql> insert into btest (age,name)values(rand(),'zhaohui'); mysql> show binlog events in 'bin-log.000003'; +----------------+-----+-------------+-----------+-------------+------------------------------------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+-----+-------------+-----------+-------------+------------------------------------------------------------------+ ...... | bin-log.000003 | 342 | Query | 1 | 410 | BEGIN | | bin-log.000003 | 410 | Intvar | 1 | 438 | INSERT_ID=3 | | bin-log.000003 | 438 | RAND | 1 | 473 | rand_seed1=223769196,rand_seed2=1013907192 | | bin-log.000003 | 473 | Query | 1 | 588 | use `test`; insert into btest (age,name)values(rand(),'zhaohui') | | bin-log.000003 | 588 | Xid | 1 | 615 | COMMIT /* xid=48 */ | +----------------+-----+-------------+-----------+-------------+------------------------------------------------------------------+ 10 rows in set (0.00 sec) |
15.USER_VAR_EVENT
執行包含了使用者變數的語句產生此事件，此事件沒有被用在binlog_format為ROW模式的情況下；
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
mysql> set @age=50; Query OK, 0 rows affected (0.00 sec) mysql> insert into btest (age,name)values(@age,'zhaohui'); Query OK, 1 row affected (0.12 sec) mysql> show binlog events in 'bin-log.000003'; +----------------+-----+-------------+-----------+-------------+------------------------------------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+-----+-------------+-----------+-------------+------------------------------------------------------------------+ ...... | | bin-log.000003 | 615 | Query | 1 | 683 | BEGIN | | bin-log.000003 | 683 | Intvar | 1 | 711 | INSERT_ID=4 | | bin-log.000003 | 711 | User var | 1 | 756 | @`age`=50 | | bin-log.000003 | 756 | Query | 1 | 869 | use `test`; insert into btest (age,name)values(@age,'zhaohui') | | bin-log.000003 | 869 | Xid | 1 | 896 | COMMIT /* xid=70 */ | +----------------+-----+-------------+-----------+-------------+------------------------------------------------------------------+ 15 rows in set (0.00 sec) |
16.FORMAT_DESCRIPTION_EVENT
描述事件，被寫在每個binlog檔案的開始位置，用在MySQL5.0以後的版本中，代替了START_EVENT_V3
|
1 2 3 4 5 6 |
mysql> show binlog events in 'bin-log.000003'; +----------------+-----+-------------+-----------+-------------+---------------------------------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+-----+-------------+-----------+-------------+---------------------------------------------------------------+ | bin-log.000003 | 4 | Format_desc | 1 | 107 | Server ver: 5.5.29-log, Binlog ver: 4 | ...... |
17.XID_EVENT
支援XA的儲存引擎才有，本地測試的資料庫儲存引擎是innodb，所有上面出現了XID_EVENT；innodb事務提交產生了QUERY_EVENT的BEGIN宣告，QUERY_EVENT以及COMMIT宣告，
如果是myIsam儲存引擎也會有BEGIN和COMMIT宣告，只是COMMIT型別不是XID_EVENT；
18.BEGIN_LOAD_QUERY_EVENT和EXECUTE_LOAD_QUERY_EVENT
執行LOAD DATA INFILE 語句時產生此事件，在MySQL5.0版本中使用；
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
mysql> LOAD DATA INFILE "D:/btest.sql" INTO TABLE test.btest FIELDS TERMINATED BY ','; Query OK, 1 row affected (0.11 sec) Records: 1 Deleted: 0 Skipped: 0 Warnings: 0 mysql> show binlog events in 'bin-log.000003'; +----------------+------+--------------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+------+--------------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ...... | | bin-log.000003 | 896 | Query | 1 | 964 | BEGIN | | bin-log.000003 | 964 | Begin_load_query | 1 | 1008 | ;file_id=3;block_len=21 | | bin-log.000003 | 1008 | Execute_load_query | 1 | 1237 | use `test`; LOAD DATA INFILE 'D:/btest.sql' INTO TABLE `btest` FIELDS TERMINATED BY ',' ENCLOSED BY '' ESCAPED BY '\\' LINES TERMINATED BY '\n' (`id`, `age`, `name`) ;file_id=3 | | bin-log.000003 | 1237 | Xid | 1 | 1264 | COMMIT /* xid=148 */ | +----------------+------+--------------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 19 rows in set (0.00 sec) |
btest.sql內容如下：
|
1 |
999, 101, 'zhaohui' |
19.TABLE_MAP_EVENT
用在binlog_format為ROW模式下，將表的定義對映到一個數字，在行操作事件之前記錄（包括：WRITE_ROWS_EVENT，UPDATE_ROWS_EVENT，DELETE_ROWS_EVENT）；
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
mysql> insert into btest values(998,88,'zhaohui'); Query OK, 1 row affected (0.09 sec) mysql> show binlog events in 'bin-log.000004'; +----------------+-----+-------------+-----------+-------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+-----+-------------+-----------+-------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ...... | | bin-log.000004 | 776 | Query | 1 | 844 | BEGIN | | bin-log.000004 | 844 | Table_map | 1 | 892 | table_id: 33 (test.btest) | | bin-log.000004 | 892 | Write_rows | 1 | 943 | table_id: 33 flags: STMT_END_F | | bin-log.000004 | 943 | Xid | 1 | 970 | COMMIT /* xid=20 */ | +----------------+-----+-------------+-----------+-------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 14 rows in set (0.00 sec) |
20.PRE_GA_WRITE_ROWS_EVENT,PRE_GA_UPDATE_ROWS_EVENT和PRE_GA_DELETE_ROWS_EVENT
以上三個事件已經過期，被其他事件代替；
PRE_GA_WRITE_ROWS_EVENT被WRITE_ROWS_EVENT代替；
PRE_GA_UPDATE_ROWS_EVENT被UPDATE_ROWS_EVENT代替；
PRE_GA_DELETE_ROWS_EVENT被DELETE_ROWS_EVENT代替；
21.WRITE_ROWS_EVENT、UPDATE_ROWS_EVENT和DELETE_ROWS_EVENT
以上三個事件都被用在binlog_format為ROW模式下，分別對應inset，update和delete操作；
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
mysql> insert into btest values(997,88,'zhaohui'); mysql> update btest set age=89 where id=997; mysql> delete from btest where id=997; mysql> show binlog events in 'bin-log.000004'; +----------------+------+-------------+-----------+-------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +----------------+------+-------------+-----------+-------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ...... | | bin-log.000004 | 1164 | Query | 1 | 1232 | BEGIN | | bin-log.000004 | 1232 | Table_map | 1 | 1280 | table_id: 33 (test.btest) | | bin-log.000004 | 1280 | Write_rows | 1 | 1331 | table_id: 33 flags: STMT_END_F | | bin-log.000004 | 1331 | Xid | 1 | 1358 | COMMIT /* xid=24 */ | | bin-log.000004 | 1358 | Query | 1 | 1426 | BEGIN | | bin-log.000004 | 1426 | Table_map | 1 | 1474 | table_id: 33 (test.btest) | | bin-log.000004 | 1474 | Update_rows | 1 | 1548 | table_id: 33 flags: STMT_END_F | | bin-log.000004 | 1548 | Xid | 1 | 1575 | COMMIT /* xid=25 */ | | bin-log.000004 | 1575 | Query | 1 | 1643 | BEGIN | | bin-log.000004 | 1643 | Table_map | 1 | 1691 | table_id: 33 (test.btest) | | bin-log.000004 | 1691 | Delete_rows | 1 | 1742 | table_id: 33 flags: STMT_END_F | | bin-log.000004 | 1742 | Xid | 1 | 1769 | COMMIT /* xid=27 */ | +----------------+------+-------------+-----------+-------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ |
22.INCIDENT_EVENT
主伺服器發生了不正常的事件，通知從伺服器並告知可能會導致資料處於不一致的狀態；
23.HEARTBEAT_LOG_EVENT
主伺服器告訴從伺服器，主伺服器還活著，不寫入到日誌檔案中；
總結
本文對Binlog的所有事件進行了大體的介紹，必要的時候也介紹了觸發事件的條件；但是並沒有深入介紹事件的fix data和variable data，後續文章會繼續介紹這一塊。
參考：
https://dev.mysql.com/doc/internals/en/event-meanings.html