Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSTGH-0001yE-A6 for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Nov 2019 21:54:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSTGG-0004Ex-1O for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Nov 2019 21:54:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSTGF-0004Eq-Ow for pgsql-hackers@lists.postgresql.org; Wed, 06 Nov 2019 21:54:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSTGC-0000rx-QU for pgsql-hackers@lists.postgresql.org; Wed, 06 Nov 2019 21:54:43 +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 xA6LscIE025295 for ; Wed, 6 Nov 2019 16:54:38 -0500 From: Tom Lane To: pgsql-hackers@lists.postgresql.org Subject: SKIP_LOCKED test causes random buildfarm failures MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25293.1573077278.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Nov 2019 16:54:38 -0500 Message-ID: <25294.1573077278@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Every once in awhile we get failures like this one: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dgull&dt=3D2019-1= 1-05%2008%3A27%3A27 diff -U3 /home/pgsql/build-farm/buildroot-clang/HEAD/pgsql.build/../pgsql/= src/test/regress/expected/vacuum.out /home/pgsql/build-farm/buildroot-clan= g/HEAD/pgsql.build/src/test/regress/results/vacuum.out --- /home/pgsql/build-farm/buildroot-clang/HEAD/pgsql.build/../pgsql/src/t= est/regress/expected/vacuum.out 2019-08-11 03:02:18.921535948 -0700 +++ /home/pgsql/build-farm/buildroot-clang/HEAD/pgsql.build/src/test/regre= ss/results/vacuum.out 2019-11-05 00:50:42.381244885 -0800 @@ -204,6 +204,7 @@ -- SKIP_LOCKED option VACUUM (SKIP_LOCKED) vactst; VACUUM (SKIP_LOCKED, FULL) vactst; +WARNING: skipping vacuum of "vactst" --- lock not available ANALYZE (SKIP_LOCKED) vactst; -- ensure VACUUM and ANALYZE don't have a problem with serializable SET default_transaction_isolation =3D serializable; No doubt this is a conflict with autovacuum. There are two reasonable ways to remove the test instability: * Crank up client_min_messages to more than WARNING for this test stanza. * Downgrade the "skipping" messages to DEBUG1 or less. I kind of wonder why we are issuing a "WARNING" when the statement does exactly what you asked it to, anyway. At most I'd expect that to be a NOTICE condition. regards, tom lane