Tom Lane wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> > I think we could solve this by putting in the same parallel group only
> > slow tests that mostly sleeps, ie. nothing that would monopolize CPU for
> > long enough to cause a problem. Concretely:
> > test: timeouts tuplelock-update deadlock-hard deadlock-soft-2
>
> OK, but there'd better be a comment there explaining the concern
> very precisely, or somebody will break it.
Here's a concrete proposal. Runtime is 45.7 seconds on my laptop. It
can be further reduced, but not by more than a second or two unless you
get in the business of modifying other tests. (I only modified
deadlock-soft-2 because it saves 5 seconds).
Admittedly the new isolation_schedule file is a bit ugly.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
