mirror of
https://github.com/MariaDB/server.git
synced 2025-08-06 02:21:34 +02:00
bbb34114ed
Ensure that Annotate_rows is always written direct after GTID information, before any table_map events. Before this patch, the following problems existed when mixing transactional and not transactional tables in the same statement: - Annotate rows could be written after row events or in the next GTID event. - See rpl_row_mixing_engines - Annotate_rows was not always written to binary log in case of error with a transactional table (rolled back) but not transactinal table was updated. - See sp_trans_log, binlog_row_mix_innodb_myisam - Annotate_rows could be written multiple times for same event. - See rpl_non_direct_mixed_mixing_engines Fixed by writing the Annotate_rows event into the non transactional cache if there arenon transactional tables used. If not, write the event into the transactional cache. |
||
|---|---|---|
| .. | ||
| archive | ||
| blackhole | ||
| columnstore | ||
| connect | ||
| csv | ||
| example | ||
| federated | ||
| federatedx | ||
| heap | ||
| innobase | ||
| maria | ||
| mroonga | ||
| myisam | ||
| myisammrg | ||
| oqgraph | ||
| perfschema | ||
| rocksdb | ||
| sequence | ||
| sphinx | ||
| spider | ||
| test_sql_discovery | ||