mariadb/mysql-test/suite/innodb
mariadb-DebarunBanerjee 7f77041b0a MDEV-37141 DML committed within XA transaction block after deadlock error and implicit rollback
Issue: When XA transaction is implicitly rolled back, we keep XA state
XA_ACTIVE and set rm_error to ER_LOCK_DEADLOCK. Other than XA command
we don't check for rm_error and DML and query are executed with a new
transaction.

Fix: One way to fix this issue is to set the XA state to XA_ROLLBACK_ONLY
which is checked while opening table open_tables() and ER_XAER_RMFAIL is
returned for any DML or Query.
2025-07-10 13:37:03 +05:30
..
include Merge branch '10.6' into 10.11 2024-05-10 20:02:18 +02:00
r MDEV-37141 DML committed within XA transaction block after deadlock error and implicit rollback 2025-07-10 13:37:03 +05:30
t MDEV-37141 DML committed within XA transaction block after deadlock error and implicit rollback 2025-07-10 13:37:03 +05:30