mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 11:01:52 +01:00
bf261cdb6f
switching binlog format to ROW BUG 52616 fixed the case which the user would switch from STMT to ROW binlog format, but the server would silently ignore it. After that fix thd->is_current_stmt_binlog_format_row() reports correct value at logging time and events are logged in ROW (as expected) instead of STMT as they were previously and wrongly logged. However, the fix was only partially complete, because on disconnect, at THD cleanup, the implicit logging of temporary tables is conditionally performed. If the binlog_format==ROW and thd->is_current_stmt_binlog_format_row() is true then DROPs are not logged. Given that the user can switch from STMT to ROW, this is wrong because the server cannot tell, just by relying on the ROW binlog format, that the tables have been dropped before. This is effectively similar to the MIXED scenario when a switch from STMT to ROW is triggered. We fix this by removing this condition from close_temporary_tables. |
||
|---|---|---|
| .. | ||
| binlog.test | ||
| binlog_insert_delayed.test | ||
| binlog_truncate.test | ||
| blackhole.test | ||
| ctype_cp932.test | ||
| ctype_cp932_binlog.test | ||
| ctype_ucs_binlog.test | ||
| database.test | ||
| drop_table.test | ||
| drop_temp_table.test | ||
| implicit.test | ||
| innodb_stat.test | ||
| insert_select-binlog.test | ||
| mix_innodb_myisam_binlog.test | ||
| mix_innodb_myisam_side_effects.test | ||