mariadb/mysql-test/suite/binlog
Brandon Nesterenko cfe91d97c8 MDEV-37737: SIGABRT upon executing BINLOG statement
An assertion would trigger at the end of the BINLOG statement execution
logic that the number of actually opened/locked tables wasn't equal
to the RGI's internal counter. This was because a piece of cleanup
code was skipped in Rows_log_event::do_apply_event() if there was a
wrong column usage. That is, instead of going to the "err" label and
doing the proper cleanup, the code (added in MDEV-36290) would
immediately DBUG_RETURN.

Fixed by switching the DBUG_RETURN to a goto err statement, and
setting the "error" variable.
2025-10-10 13:01:28 -06:00
..
include Merge branch '10.11' into 11.4 2025-07-28 19:40:10 +02:00
r MDEV-37737: SIGABRT upon executing BINLOG statement 2025-10-10 13:01:28 -06:00
std_data MDEV-30128 remove support for 5.1- replication events 2023-02-05 22:02:30 +01:00
t MDEV-37737: SIGABRT upon executing BINLOG statement 2025-10-10 13:01:28 -06:00
combinations WL#4350 Options in my.cnf style config file should not start with -- 2008-09-05 15:31:09 +02:00
disabled.def MDEV-30940: Revert "binlog.innodb_rc_insert_before_delete is disabled with MDEV-30490" 2023-01-30 21:28:21 +01:00
my.cnf MDEV-31404 Implement binlog_space_limit 2024-02-14 15:02:21 +01:00