| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| 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:24:28 |
| Message-ID: | 1681.1420064668@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> 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.
I'd be fine with reverting this commit if Stephen wants to refactor the
rowsecurity/event_trigger tests that way. Dunno if it makes sense to
do that though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-01-02 13:47:29 | Re: pgsql: Don't run rowsecurity in parallel with other regression tests. |
| Previous Message | Tom Lane | 2014-12-31 22:17:59 | Re: Re: [COMMITTERS] pgsql: pg_event_trigger_dropped_objects: Add name/args output columns |