1
0
mirror of https://github.com/MariaDB/server.git synced 2025-11-06 13:10:12 +03:00
Files
mariadb/mysql-test/suite/innodb/r
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
..
2022-09-20 16:53:20 +03:00
2022-09-20 16:53:20 +03:00
2023-12-18 08:59:07 +02:00
2024-03-12 09:19:57 +02:00
2025-02-25 10:23:24 +02:00
2021-11-16 16:30:45 +02:00
2022-09-13 16:36:38 +03:00
2024-02-07 13:51:03 +02:00
2022-04-13 13:39:00 +03:00
2024-01-03 15:37:57 +02:00
2025-04-07 10:25:34 +03:00
2022-09-13 16:36:38 +03:00
2022-09-21 10:59:56 +03:00
2022-09-21 09:33:07 +03:00
2022-09-13 16:36:38 +03:00
2022-09-20 16:53:20 +03:00
2022-09-13 16:36:38 +03:00
2023-11-30 10:45:01 +02:00
2022-09-20 16:53:20 +03:00
2022-09-20 16:53:20 +03:00
2022-09-13 16:36:38 +03:00
2023-11-30 10:45:01 +02:00
2024-10-03 10:55:08 +03:00
2023-04-11 16:15:19 +03:00
2025-01-30 11:55:13 +01:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-11-30 12:12:07 +02:00
2024-04-22 15:23:10 +02:00
2024-06-10 15:22:15 +03:00
2024-10-03 09:31:39 +03:00
2024-03-12 09:19:57 +02:00
2024-05-30 14:27:07 +03:00
2022-09-21 09:52:09 +03:00
2024-02-21 13:08:23 +02:00
2022-09-20 16:53:20 +03:00
2024-05-30 14:27:07 +03:00