| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] big test separation POC |
| Date: | 2013-07-11 18:56:46 |
| Message-ID: | alpine.DEB.2.02.1307112053210.11644@localhost6.localdomain6 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The other option, suggested by Andres somewhere, is to have a new
> parameter to pg_regress, something like --run-serially.
After looking at the source, ISTM that this option already exists under a
different signature:
--max-connections 1
> So you would use the same parallel schedule file, but serially instead
> of following the parallel specification.
Yep. And there is nothing to do, which is even better:-)
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-07-11 19:09:45 | Re: mvcc catalo gsnapshots and TopTransactionContext |
| Previous Message | Jeff Davis | 2013-07-11 18:53:57 | Re: mvcc catalo gsnapshots and TopTransactionContext |