Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. - Mailing list pgsql-hackers

From Greg Stark
Subject Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
Date
Msg-id CAM-w4HOuJPZKN4cgSq8d=8t078X3epXUy1jTTnSDp3vUyv9MJg@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
List pgsql-hackers
<p dir="ltr">The tests worked fine on faster build animals, right? And the clobber animals are much much slower.... So
itseems perfectly sensible that their deadlock timeout would just have to be much much higher to have the same
behaviour.I see nothing wrong in just setting deadlock timeout to a minute or more on these machines. <p dir="ltr">The
invariantis just that the deadlock timeout needs enough head room over the actual time the tester's queries take. If
theynormally take a 1/10th of a second then why not just set the timeout to 10x however long they take on the clobber
animals?<pdir="ltr">-- <br /> Greg 

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Defaults for replication/backup
Next
From: Michael Paquier
Date:
Subject: Re: GinPageIs* don't actually return a boolean