Re: pgsql: Address portability issues in bfe16d1a5 test output.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Address portability issues in bfe16d1a5 test output.
Date: 2016-09-13 01:33:03
Message-ID: 27946.1473730383@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2016-09-12 21:25:05 -0400, Tom Lane wrote:
>> Hm, lapwing says this can't run in parallel with "misc" either :-(

> Gah. That's probably why I had originally had it running in the rules
> group. But isn't that user_relns() test just a bad idea independent of
> this failure? I mean what's the benefit of returning all relations
> there, besides causing regression test churn?

It looks like making your tables temp would work around it ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2016-09-13 01:35:37 Re: pgsql: Address portability issues in bfe16d1a5 test output.
Previous Message Andres Freund 2016-09-13 01:32:13 Re: pgsql: Address portability issues in bfe16d1a5 test output.