Let's get rid of serial_schedule

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Date: 2021-05-11T18:58:26Z
Lists: pgsql-hackers

Attachments

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

Commits

  1. Fix vcregress.pl's ancient misspelling of --max-connections.

  2. Get rid of the separate serial_schedule list of tests.