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
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2011-09-21 02:18:45|
|Subject: Re: EXPLAIN and nfiltered, take two|
|Previous:||From: Dan McGee||Date: 2011-09-21 01:54:20|
|Subject: [PATCH] POC: inline int4 comparison in tuplesort|