Re: pgsql: Don't run rowsecurity in parallel with other regression tests.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Don't run rowsecurity in parallel with other regression tests.
Date: 2014-12-31 22:12:07
Message-ID: 20141231221207.GE1457@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Tom Lane wrote:
> Don't run rowsecurity in parallel with other regression tests.
>
> The short-lived event trigger in the rowsecurity test causes irreproducible
> failures when the concurrent tests do something that the event trigger
> can't cope with. Per buildfarm.

Ah, so this explains the failures.

I wonder if it'd be better to remove the event trigger bits from that
test, and put them (if we really need them) in the event_trigger test.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2014-12-31 22:17:59 Re: Re: [COMMITTERS] pgsql: pg_event_trigger_dropped_objects: Add name/args output columns
Previous Message Alvaro Herrera 2014-12-31 22:09:49 Re: Re: [COMMITTERS] pgsql: pg_event_trigger_dropped_objects: Add name/args output columns