pgsql: Increase deadlock_timeout some more in the deadlock-hard isolati

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Increase deadlock_timeout some more in the deadlock-hard isolati
Date: 2016-02-12 22:22:49
Message-ID: E1aUM6z-00035C-Ff@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Increase deadlock_timeout some more in the deadlock-hard isolation test.

The previous value of 5s is inadequate for the buildfarm's
CLOBBER_CACHE_ALWAYS animals: they take long enough to do the is-it-waiting
queries that the timeout expires, allowing the database state to change,
before isolationtester is done looking. Perhaps 10s will be enough.
(If it isn't, I'm inclined to reduce the number of sessions involved.)

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/e84e06d2b3fc48c514fd44f7ac390eb5f3e20d72

Modified Files
--------------
src/test/isolation/specs/deadlock-hard.spec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Joe Conway 2016-02-12 22:24:27 pgsql: Change delimiter used for display of NextXID
Previous Message Tom Lane 2016-02-12 22:12:30 pgsql: Revert "Still further tweaking of deadlock isolation tests."