mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 02:51:44 +01:00
42802ad66c
the only query of the XA transaction is on a non-transactional table errors out: XA BEGIN 'x'; --error ER_DUP_ENTRY INSERT INTO t1 VALUES (1),(1); XA END 'x'; XA PREPARE 'x'; The binlogging pattern is correctly started as expected with the errored-out Query or its ROW format events, but there is no empty XA_prepare_log_event group. The following XA COMMIT 'x'; therefore should not be logged either, but it does. The bug is fixed with proper maintaining of a read-write binlog hton property and use it to enforce correct binlogging decisions. Specifically in the bug description case XA COMMIT won't be binlogged in both when given in the same connection and externally after disconnect. The same continue to apply to an empty XA that do not change any data in all transactional engines involved.
18 lines
250 B
INI
18 lines
250 B
INI
!include include/default_mysqld.cnf
|
|
|
|
[mysqld.1]
|
|
log-slave-updates
|
|
innodb
|
|
|
|
[mysqld.2]
|
|
log-slave-updates
|
|
innodb
|
|
|
|
[mysqld.3]
|
|
log-slave-updates
|
|
innodb
|
|
|
|
[ENV]
|
|
SERVER_MYPORT_1= @mysqld.1.port
|
|
SERVER_MYPORT_2= @mysqld.2.port
|
|
SERVER_MYPORT_3= @mysqld.3.port
|