database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-18 04:29:09 +03:00
Code Activity

Revert "Still further tweaking of deadlock isolation tests."

Browse Source 
This reverts commit d03130d378.
That was dependent on an isolationtester.c change that now proves
to be broken; we will need to find another solution.
This commit is contained in:
Tom Lane
2016-02-12 17:02:59 -05:00
parent 34f13cc484
commit 3992188c2a
2 changed files with 5 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/test/isolation/specs/deadlock-hard.spec
View File

@@ -1,9 +1,7 @@
# This is a straightforward deadlock scenario. Since it involves more than
# two processes, the main lock detector will find the problem and rollback
# the session that first discovers it. Set deadlock_timeout in each session
# so that it's predictable which session fails. Also, when s8 fails and
# rolls back, it unblocks s7, so that there is a race as to whether s7a8
# or s8a1 will report first. Add a delay in s7a8 to make that predictable.
# so that it's predictable which session fails.
setup
{
@@ -61,7 +59,7 @@ step "s6c" { COMMIT; }
session "s7"
setup { BEGIN; SET deadlock_timeout = '100s'; }
step "s7a7" { LOCK TABLE a7; }
step "s7a8" { LOCK TABLE a8; SELECT pg_sleep(5); }
step "s7a8" { LOCK TABLE a8; }
step "s7c" { COMMIT; }
session "s8"