From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Let's get rid of serial_schedule |
Date: | 2021-05-11 18:58:26 |
Message-ID: | 899209.1620759506@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
(The vcregress.pl changes are untested, but they seem straightforward
enough. I do wonder though why we spell it --max-concurrent-tests
there when the makefile uses --max-connections.)
It'd perhaps be possible to adjust pg_regress so that when
--max-connections=1 its progress output looks exactly the same
as it did with serial_schedule. I doubt it's worth the trouble
though, unless anyone really wants that.
Any objections?
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
delete-serial_schedule.patch | text/x-diff | 6.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2021-05-11 19:11:32 | Re: Let's get rid of serial_schedule |
Previous Message | Andrew Dunstan | 2021-05-11 18:46:35 | Re: Performance degradation of REFRESH MATERIALIZED VIEW |