Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2.36, 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
-
None
Description
|
connection1 |
MariaDB [test]> create table t ( i int primary key);
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
MariaDB [test]> XA START 'test';
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
MariaDB [test]> insert into t values (41), (3324),(14);
|
Query OK, 3 rows affected (0.00 sec)
|
Records: 3 Duplicates: 0 Warnings: 0
|
|
|
connection2 |
MariaDB [(none)]> set global read_only=1;
|
Query OK, 0 rows affected (0.00 sec)
|
|
connection1 |
MariaDB [test]> XA END 'test';
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
MariaDB [test]> XA PREPARE 'test';
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
MariaDB [test]> XA COMMIT 'test';
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
MariaDB [test]> select * from t;
|
+------+
|
| i |
|
+------+
|
| 14 |
|
| 41 |
|
| 3324 |
|
+------+
|
3 rows in set (0.00 sec)
|
|
A non-XA transaction would of errored on the `COMMIT`. XA has no such limitations.