aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2016-08-18 17:30:14 -0700
committerAndres Freund <andres@anarazel.de>2016-08-18 17:34:05 -0700
commit9595383bc6fc24d25970374e2eddd5ce6f977f9e (patch)
tree2fd3c3b8af0227b50f69dcbfed588631cd0e80d1 /src
parent1d2e73a3dfdbd7168b323fa39879c60df6076412 (diff)
downloadpostgresql-9595383bc6fc24d25970374e2eddd5ce6f977f9e.tar.gz
postgresql-9595383bc6fc24d25970374e2eddd5ce6f977f9e.zip
Add alternative output for ON CONFLICT toast isolation test.
On some buildfarm animals the isolationtest added in 07ef0351 failed, as the order in which processes are run after unlocking is not guaranteed. Add an alternative output for that. Discussion: <7969.1471484738@sss.pgh.pa.us> Backpatch: 9.6, like the test in the aforementioned commit
Diffstat (limited to 'src')
-rw-r--r--src/test/isolation/expected/insert-conflict-toast_1.out15
1 files changed, 15 insertions, 0 deletions
diff --git a/src/test/isolation/expected/insert-conflict-toast_1.out b/src/test/isolation/expected/insert-conflict-toast_1.out
new file mode 100644
index 00000000000..18346162b7e
--- /dev/null
+++ b/src/test/isolation/expected/insert-conflict-toast_1.out
@@ -0,0 +1,15 @@
+Parsed test spec with 3 sessions
+
+starting permutation: s2insert s3insert s1commit
+pg_advisory_xact_lock
+
+
+step s2insert:
+ INSERT INTO ctoast (key, val) VALUES (1, ctoast_large_val()) ON CONFLICT DO NOTHING;
+ <waiting ...>
+step s3insert:
+ INSERT INTO ctoast (key, val) VALUES (1, ctoast_large_val()) ON CONFLICT DO NOTHING;
+ <waiting ...>
+step s1commit: COMMIT;
+step s3insert: <... completed>
+step s2insert: <... completed>