| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Don't run rowsecurity in parallel with other regression tests. |
| Date: | 2015-01-02 14:42:55 |
| Message-ID: | 20150102144255.GG1457@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Stephen Frost wrote:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> > 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.
>
> I'll move the event trigger in the rowsecurity tests over to the
> event_trigger test and then move the rowsecurity tests back into the
> parallel group.
>
> Please let me know if there's any concerns with this approach.
Sounds good to me, thanks.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2015-01-03 12:22:07 | pgsql: Make path to pg_service.conf absolute in documentation |
| Previous Message | Stephen Frost | 2015-01-02 13:47:29 | Re: pgsql: Don't run rowsecurity in parallel with other regression tests. |