pgsql: Don't run fast_default regression test in parallel with other te

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Don't run fast_default regression test in parallel with other te
Date: 2018-04-20 21:28:02
Message-ID: E1f9dZa-0001HP-4p@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't run fast_default regression test in parallel with other tests.

Since it sets up an event trigger that would fire on DDL done by any
concurrent test script, the original scheduling is just an invitation
to irreproducible test failures. (The fact that we found a bug through
exactly such irreproducible test failures doesn't really change the
calculus here: this script is a hazard to anything that runs in parallel
with it today or might be added to that parallel group in future. No,
I don't believe that the trigger is protecting itself sufficiently to
avoid all possible trouble.)

Discussion: https://postgr.es/m/5767.1523995174@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/676858bcb4c4d9d2d5ee63a87dbff01085984ee0

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

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2018-04-20 23:05:19 pgsql: Fix a couple minor typos
Previous Message Tom Lane 2018-04-20 21:15:45 pgsql: Fix race conditions when an event trigger is added concurrently