mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
60a2bbb8dd
"freeing items" The calculation of the table map log event in the event constructor was one byte shorter than what would be actually written. This would lead to a mismatch between the number of bytes written and the event end_log_pos, causing bad event alignment in the binlog (corrupted binlog) or in the transaction cache while fixing positions (MYSQL_BIN_LOG::write_cache). This could lead to impossible to read binlog or even infinite loops in MYSQL_BIN_LOG::write_cache. This patch addresses this issue by correcting the expected event length in the Table_map_log_event constructor, when the field metadata size exceeds 255. sql/log_event.cc: Added the extra byte as net_store_length imposes. |
||
---|---|---|
.. | ||
binlog_auto_increment_bug33029.result | ||
binlog_base64_flag.result | ||
binlog_database.result | ||
binlog_grant.result | ||
binlog_index.result | ||
binlog_innodb.result | ||
binlog_innodb_row.result | ||
binlog_killed.result | ||
binlog_killed_simulate.result | ||
binlog_mix_innodb_stat.result | ||
binlog_multi_engine.result | ||
binlog_old_versions.result | ||
binlog_row_binlog.result | ||
binlog_row_ctype_cp932.result | ||
binlog_row_ctype_ucs.result | ||
binlog_row_drop_tmp_tbl.result | ||
binlog_row_innodb_stat.result | ||
binlog_row_insert_select.result | ||
binlog_row_mix_innodb_myisam.result | ||
binlog_sql_mode.result | ||
binlog_start_comment.result | ||
binlog_statement_insert_delayed.result | ||
binlog_stm_binlog.result | ||
binlog_stm_blackhole.result | ||
binlog_stm_ctype_cp932.result | ||
binlog_stm_ctype_ucs.result | ||
binlog_stm_drop_tmp_tbl.result | ||
binlog_stm_innodb_stat.result | ||
binlog_stm_insert_select.result | ||
binlog_stm_mix_innodb_myisam.result | ||
binlog_stm_ps.result | ||
binlog_stm_row.result | ||
binlog_tbl_metadata.result | ||
binlog_tmp_table.result | ||
binlog_truncate_innodb.result | ||
binlog_truncate_myisam.result | ||
binlog_unsafe.result |