summaryrefslogtreecommitdiff
path: root/mysql-test/main/consistent_snapshot.result
diff options
context:
space:
mode:
Diffstat (limited to 'mysql-test/main/consistent_snapshot.result')
-rw-r--r--mysql-test/main/consistent_snapshot.result44
1 files changed, 44 insertions, 0 deletions
diff --git a/mysql-test/main/consistent_snapshot.result b/mysql-test/main/consistent_snapshot.result
new file mode 100644
index 00000000000..b978f1dd9d2
--- /dev/null
+++ b/mysql-test/main/consistent_snapshot.result
@@ -0,0 +1,44 @@
+DROP TABLE IF EXISTS t1;
+connect con1,localhost,root,,;
+connect con2,localhost,root,,;
+### Test 1:
+### - While a consistent snapshot transaction is executed,
+### no external inserts should be visible to the transaction.
+connection con1;
+CREATE TABLE t1 (a INT) ENGINE=innodb;
+START TRANSACTION WITH CONSISTENT SNAPSHOT;
+connection con2;
+INSERT INTO t1 VALUES(1);
+connection con1;
+SELECT * FROM t1;
+a
+COMMIT;
+### Test 2:
+### - For any non-consistent snapshot transaction, external
+### committed inserts should be visible to the transaction.
+DELETE FROM t1;
+START TRANSACTION;
+connection con2;
+INSERT INTO t1 VALUES(1);
+connection con1;
+SELECT * FROM t1;
+a
+1
+COMMIT;
+### Test 3:
+### - Bug#44664: valgrind warning for COMMIT_AND_CHAIN and ROLLBACK_AND_CHAIN
+### Chaining a transaction does not retain consistency level.
+START TRANSACTION WITH CONSISTENT SNAPSHOT;
+DELETE FROM t1;
+COMMIT WORK AND CHAIN;
+connection con2;
+INSERT INTO t1 VALUES(1);
+connection con1;
+SELECT * FROM t1;
+a
+1
+COMMIT;
+connection default;
+disconnect con1;
+disconnect con2;
+DROP TABLE t1;