From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Let's get rid of serial_schedule |
Date: | 2021-05-11 19:11:32 |
Message-ID: | 5C862D45-668B-4DC2-AE63-135140041E5F@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 11 May 2021, at 20:58, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> We've several times discussed doing $SUBJECT by replacing the
> makefile's use of serial_schedule with calling parallel_schedule
> with --max-connections=1. This'd remove the need to maintain
> two lists of regression test scripts.
>
> I got annoyed again just now about how people seem unable to
> keep the two lists in the same order, so here is a patch to
> get rid of serial_schedule in that way.
Very much +1 on this approach.
> + # for backwards compatibility, interpret "serial" as parallel tests
This comment may seem odd without reading the commit message. Perhaps it can
be reworded to "..as parallel tests running with a single worker" or something
along those lines?
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2021-05-11 19:12:46 | Re: Let's get rid of serial_schedule |
Previous Message | Tom Lane | 2021-05-11 18:58:26 | Let's get rid of serial_schedule |