pgsql: Bump up timeout delays some more in timeouts isolation test.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Bump up timeout delays some more in timeouts isolation test.
Date: 2013-03-20 17:54:22
Message-ID: E1UINDS-0007Li-C1@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Bump up timeout delays some more in timeouts isolation test.

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.

Branch
------
master

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

Modified Files
--------------
src/test/isolation/expected/timeouts.out | 16 ++++++++--------
src/test/isolation/specs/timeouts.spec | 8 ++++----
2 files changed, 12 insertions(+), 12 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2013-03-20 21:20:23 pgsql: Allow extracting machine-readable object identity
Previous Message Kevin Grittner 2013-03-19 15:35:05 pgsql: Use ORDER BY on matview definitions were needed for stable plans