pgsql: Clean up sloppy maintenance of regression test schedule files.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Clean up sloppy maintenance of regression test schedule files.
Date: 2017-10-07 17:19:20
Message-ID: E1e0sky-0003P5-5f@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-10-07 21:20:16 pgsql: Enforce our convention about max number of parallel regression t
Previous Message Alvaro Herrera 2017-10-07 08:31:06 Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple