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

Bump up timeout delays some more in timeouts isolation test.

Browse Source 
The buildfarm members using -DCLOBBER_CACHE_ALWAYS still don't like this
test.  Some experimentation shows that on my machine, isolationtester's
query to check for "waiting" state takes 2 to 2.5 seconds to bind+execute
under -DCLOBBER_CACHE_ALWAYS.  Set the timeouts to 5 seconds to leave some
headroom for possibly-slower buildfarm critters.

Really we ought to fix the "waiting" query, which is not only horridly
slow but outright wrong in detail; and then maybe we can back off these
timeouts.  But right now I'm just trying to get the buildfarm green again.
This commit is contained in:
Tom Lane
2013-03-20 13:53:43 -04:00
parent 241139ae4b
commit a7921f71a3
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/test/isolation/specs/timeouts.spec
View File

@@ -19,10 +19,10 @@ teardown { ABORT; }
session "s2"
setup { BEGIN ISOLATION LEVEL READ COMMITTED; }
step "sto" { SET statement_timeout = 2000; }
step "lto" { SET lock_timeout = 2000; }
step "lsto" { SET lock_timeout = 2000; SET statement_timeout = 3000; }
step "slto" { SET lock_timeout = 3000; SET statement_timeout = 2000; }
step "sto" { SET statement_timeout = 5000; }
step "lto" { SET lock_timeout = 5000; }
step "lsto" { SET lock_timeout = 5000; SET statement_timeout = 6000; }
step "slto" { SET lock_timeout = 6000; SET statement_timeout = 5000; }
step "locktbl" { LOCK TABLE accounts; }
step "update" { DELETE FROM accounts WHERE accountid = 'checking'; }
teardown { ABORT; }