From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Some other odd buildfarm failures |
Date: | 2014-12-26 03:32:47 |
Message-ID: | 20141226033247.GA1645@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > My guess is that it's related to d7ee82e50f. It seems realistic that the
> > event trigger added by it to the object_address test can cause errors at
> > varying times.
>
> [ squint... ] Event triggers are global across the whole database, aren't
> they? Isn't it frickin insane to run a test like this in parallel with
> others?
Well, the event trigger function is BEGIN END; so I don't think it
should affect anything.
> Not but what it seems to be exposing some bugs.
That seems to me a good thing ... a bit inconvenient of course, but it
beats having users get strange behavior which they can't possibly debug.
> Still, I don't think this is a reasonable test design. We have
> absolutely no idea what behaviors are being triggered in the other
> tests, except that they are unrelated to what those tests think they
> are testing.
I can of course move it to a separate parallel test, but I don't think
that should be really necessary.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-12-26 03:49:26 | Re: Better way of dealing with pgstat wait timeout during buildfarm runs? |
Previous Message | Michael Paquier | 2014-12-26 03:31:27 | Re: [REVIEW] Re: Compression of full-page-writes |