pgsql: Fix timing-sensitive regression test result I just created :-( - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix timing-sensitive regression test result I just created :-(
Date
Msg-id 20100203032125.593837541B9@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix timing-sensitive regression test result I just created :-( --- the
DROP USER at the end of the cluster.sql test could fail, if the temp
table created in the previous session hadn't finished getting dropped.
Unluckily, I didn't see this in several repetitions of the parallel
regression tests, but it's popping up on quite a few buildfarm machines.

Modified Files:
--------------
    pgsql/src/test/regress/expected:
        cluster.out (r1.21 -> r1.22)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/cluster.out?r1=1.21&r2=1.22)
    pgsql/src/test/regress/sql:
        cluster.sql (r1.13 -> r1.14)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/cluster.sql?r1=1.13&r2=1.14)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Assorted cleanups in preparation for using a map file to support
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Add #include --- guessing the lack of this is why