Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ewFrW-0002by-EE for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Mar 2018 23:31:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ewFrV-0006NT-7g for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Mar 2018 23:31:13 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ewFrU-0006Mk-TP for pgsql-hackers@lists.postgresql.org; Wed, 14 Mar 2018 23:31:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ewFrR-0004mI-UB for pgsql-hackers@lists.postgresql.org; Wed, 14 Mar 2018 23:31:11 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w2ENV8dl004628 for ; Wed, 14 Mar 2018 19:31:08 -0400 From: Tom Lane To: pgsql-hackers@lists.postgresql.org Subject: Instability in parallel regression tests MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4626.1521070268.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 14 Mar 2018 19:31:08 -0400 Message-ID: <4627.1521070268@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk guaibasaurus just failed in a way I'd not seen before: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dguaibasaurus&dt=3D= 2018-03-14%2006%3A33%3A01 Inspection of the diffs makes it depressingly obvious what happened: the concurrently-executing "alter_table" and "with" scripts both create short-lived tables named "test". Given the right timing, those tests stomp on each other. This seems to have been there a long time; surprising we'd not noticed it before. Moral: choose names less generic than "test" for globally-visible objects. I wonder if there's some way we could check for such conflicts automatically? regards, tom lane