aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-06-15 16:11:45 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-06-15 16:11:45 -0400
commitd3c878499c9d639ff06e0664d06b8c731e30c2fc (patch)
tree74091272caf12e7848089b95f4a579b1343358cf
parentf6352a0d4e437ac8bc266f77df22d064592056c9 (diff)
downloadpostgresql-d3c878499c9d639ff06e0664d06b8c731e30c2fc.tar.gz
postgresql-d3c878499c9d639ff06e0664d06b8c731e30c2fc.zip
Update another variant expected-result file.
This should have been updated in 533e9c6b0, but it was overlooked. Given the lack of complaints, I won't bother back-patching.
-rw-r--r--src/test/isolation/expected/lock-update-delete_1.out4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/test/isolation/expected/lock-update-delete_1.out b/src/test/isolation/expected/lock-update-delete_1.out
index 4203573b9c1..f1c1c7026f4 100644
--- a/src/test/isolation/expected/lock-update-delete_1.out
+++ b/src/test/isolation/expected/lock-update-delete_1.out
@@ -150,7 +150,9 @@ pg_advisory_unlock
t
step s1l: <... completed>
-error in steps s2_unlock s1l: ERROR: could not serialize access due to concurrent update
+key value
+
+1 1
starting permutation: s2b s1l s2u s2_blocker1 s2r s2_unlock
pg_advisory_lock