From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Isolation tests still falling over routinely |
Date: | 2011-09-21 02:04:45 |
Message-ID: | 1316570348-sup-317@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Kevin Grittner's message of mar sep 20 22:51:39 -0300 2011:
> If I remember right, Alvaro chose these timings to balance run time
> against chance of failure. Unless we want to remove these deadlock
> handling tests or ignore failures (which both seem like bad ideas to
> me), I think we need to bump the long timings by an order of
> magnitude and just concede that those tests run for a while.
The main problem I have is that I haven't found a way to reproduce the
problems in my machine. I was playing with modifying the way the error
messages are reported, but that ended up unfinished in a local branch.
I'll give it a go once more and see if I can commit so that buildfarm
tells us if it works or not.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-09-21 02:18:45 | Re: EXPLAIN and nfiltered, take two |
Previous Message | Dan McGee | 2011-09-21 01:54:20 | [PATCH] POC: inline int4 comparison in tuplesort |