The attached test case (3 files in total) fails as follows in current MariaDB 5.3:
main.innodb_release_locks_early_recovery [ fail ]
Test ended at 2011-06-22 10:26:18
CURRENT_TEST: main.innodb_release_locks_early_recovery
--- /home/knielsen/my/5.3/mariadb-5.3/mysql-test/r/innodb_release_locks_early_recovery.result 2011-06-22 10:26:00.000000000 +0200
+++ /home/knielsen/my/5.3/mariadb-5.3/mysql-test/r/innodb_release_locks_early_recovery.reject 2011-06-22 10:26:18.000000000 +0200
@@ -58,7 +58,7 @@
Got one of the listed errors
SELECT * FROM t1;
a b
-1 Base0
+1 Update c4
SELECT * FROM t2 ORDER by a;
a
DROP TABLE t1;
mysqltest: Result length mismatch
As explained above, we see here transaction c4 visible in table t1, even though it should have been rolled back (and is rolled back in table t2).
The attached test case (3 files in total) fails as follows in current MariaDB 5.3:
main.innodb_ release_ locks_early_ recovery [ fail ]
Test ended at 2011-06-22 10:26:18
CURRENT_TEST: main.innodb_ release_ locks_early_ recovery my/5.3/ mariadb- 5.3/mysql- test/r/ innodb_ release_ locks_early_ recovery. result 2011-06-22 10:26:00.000000000 +0200 my/5.3/ mariadb- 5.3/mysql- test/r/ innodb_ release_ locks_early_ recovery. reject 2011-06-22 10:26:18.000000000 +0200
--- /home/knielsen/
+++ /home/knielsen/
@@ -58,7 +58,7 @@
Got one of the listed errors
SELECT * FROM t1;
a b
-1 Base0
+1 Update c4
SELECT * FROM t2 ORDER by a;
a
DROP TABLE t1;
mysqltest: Result length mismatch
As explained above, we see here transaction c4 visible in table t1, even though it should have been rolled back (and is rolled back in table t2).