[COMMITTERS] pgsql: Clean up sloppy maintenance of regression test schedule files. - Mailing list pgsql-committers

From Tom Lane
Subject [COMMITTERS] pgsql: Clean up sloppy maintenance of regression test schedule files.
Date
Msg-id E1e0sky-0003P5-5f@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Clean up sloppy maintenance of regression test schedule files.

The partition_join test was added to a parallel group that was already
at the maximum of 20 concurrent tests.  The hash_func test wasn't
added to serial_schedule at all.  The identity and partition_join tests
were added to serial_schedule with the aid of a dartboard, rather than
maintaining consistency with parallel_schedule.

There are proposals afoot to make these sorts of errors harder to make,
but in the meantime let's fix the ones already in place.

Discussion: https://postgr.es/m/a37e9c57-22d4-1b82-1270-4501cd2e984e@2ndquadrant.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1fdab4d5aa47d8a2bb29ccb1122b0158f6db221f

Modified Files
--------------
src/test/regress/parallel_schedule | 4 ++--
src/test/regress/serial_schedule   | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)


--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Fix crash when logical decoding is invoked from a PL function.
Next
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Enforce our convention about max number of parallel regressiont