Re: Recent buildfarm failures involving statement_timeout

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Recent buildfarm failures involving statement_timeout
Date: 2008-04-28 14:26:22
Message-ID: 12227.1209392782@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> sysname | snapshot | branch
>> ---------+---------------------+---------------
>> lionfish | 2007-04-19 09:30:27 | REL8_2_STABLE
>> lionfish | 2007-05-29 23:30:07 | REL8_1_STABLE
>> lionfish | 2007-09-22 23:30:07 | REL8_1_STABLE

> lionfish is(or rather was - powersupply got fried and I have no
> replacement yet) one of the slowest machines(250MHZ mipsel,48MB RAM) on
> the buildfarm (took about 5-6h for a complete run).

Unless someone has a better idea, I suggest we just raise the timeouts
used in prepared_xacts from 1 sec to 2 sec. That should reduce the
recurrence rate to something vanishingly small if the problem is just
"it's too slow". If it's that something's actually getting stuck, then
we'll continue to see failures and will know that closer investigation
is needed.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-04-28 14:48:58 pgsql: Add generate_subscripts, a series-generation function which
Previous Message Andrew Sullivan 2008-04-28 14:21:08 Re: we don't have a bugzilla