Re: Suppressing occasional failures in copy2 regression test

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Suppressing occasional failures in copy2 regression test
Date: 2009-06-13 19:09:06
Message-ID: 603c8f070906131209l445505eib9e573ecf8126a7c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 13, 2009 at 2:48 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> writes:
>> I'm not sure about that. It seems like race conditions with autovacuum
>> are a real potential bug that it would be nice to be testing for.
>
> It's not a bug; it's a limitation of our testing framework that it sees
> this as a failure.  Serious testing for autovac race conditions would
> indeed be interesting, but you're never going to get anything meaningful
> in that direction out of the current framework.

The elephant in the room here may be moving to some more
flexible/powerful testing framework, but the difficulty will almost
certainly be in agreeing what it should look like. The actual writing
of said test framework will take some work too, but to some degree
that's a SMOP.

This tuple-ordering issue seems to be one that comes up over and over
again, but in the short term, making it a TEMP table seems like a
reasonable fix.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bernd Helmle 2009-06-13 22:33:31 Re: machine-readable explain output
Previous Message Robert Haas 2009-06-13 19:01:43 Re: machine-readable explain output