diff options
author | Brandon Nesterenko <brandon.nesterenko@mariadb.com> | 2022-09-14 15:08:12 -0600 |
---|---|---|
committer | Andrei <andrei.elkin@mariadb.com> | 2022-10-25 12:56:33 +0300 |
commit | 42802ad66c49b6de11b37c7ea4e4658ccc5a94aa (patch) | |
tree | 6c69907d0211e37b4285b2897cc09d5888e45043 /mysql-test/std_data | |
parent | 4b4c2b8cc0da949895292121ed5ef3e0c2dbaae1 (diff) | |
download | mariadb-git-42802ad66c49b6de11b37c7ea4e4658ccc5a94aa.tar.gz |
MDEV-25616 XA PREPARE event group is not binlogged when..
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.
Diffstat (limited to 'mysql-test/std_data')
0 files changed, 0 insertions, 0 deletions