Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mas9x-0003nk-JC for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Oct 2021 04:16:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mas9v-0005LZ-1b for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Oct 2021 04:15:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mas9u-0005LQ-P9 for pgsql-hackers@lists.postgresql.org; Thu, 14 Oct 2021 04:15:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mas9s-0007TD-CA for pgsql-hackers@postgresql.org; Thu, 14 Oct 2021 04:15:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 19E4FoBG726474; Thu, 14 Oct 2021 00:15:50 -0400 From: Tom Lane To: Peter Geoghegan cc: Mark Dilger , Robert Haas , Pavel Borisov , Alexander Lakhin , PostgreSQL-development Subject: Re: BUG #17212: pg_amcheck fails on checking temporary relations In-reply-to: References: <17212-34dd4a1d6bba98bf@postgresql.org> <28B36E41-1E8F-4DC1-A924-711621BA4972@enterprisedb.com> <386F66EE-DEFD-42EA-9DB2-102BF3414669@enterprisedb.com> <63FF68F5-683D-423E-A667-9C00441101A5@enterprisedb.com> <561CE3DB-5CBC-44BF-9A3E-1D7FAEB123E0@enterprisedb.com> <543F3BF3-EDED-4C52-AF05-623921B6C409@enterprisedb.com> <55A2BFE7-AAAF-4A64-BD3A-5C98EA982267@enterprisedb.com> <07159C9A-40DA-47BF-B2F4-! 203F5AC00890@enterprisedb.com> <40DB088B-C96F-49B2-BC84-BDC8D35C7E97@enterprisedb.com> <0B7DA7A4-2872-485B-BFDD-BF8E9BB07B26@enterprisedb.com> message dated "Wed, 13 Oct 2021 20:48:04 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <726472.1634184950.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 14 Oct 2021 00:15:50 -0400 Message-ID: <726473.1634184950@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > Any idea what the problems on drongo are? > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Ddrongo&dt=3D20= 21-10-14%2001%3A27%3A19 It says # pg_ctl start failed; logfile: 2021-10-14 02:10:33.996 UTC [491848:1] LOG: starting PostgreSQL 14.0, com= piled by Visual C++ build 1923, 64-bit 2021-10-14 02:10:33.999 UTC [491848:2] LOG: could not bind IPv4 address "= 127.0.0.1": Only one usage of each socket address (protocol/network addres= s/port) is normally permitted. 2021-10-14 02:10:33.999 UTC [491848:3] HINT: Is another postmaster alread= y running on port 54407? If not, wait a few seconds and retry. 2021-10-14 02:10:33.999 UTC [491848:4] WARNING: could not create listen s= ocket for "127.0.0.1" 2021-10-14 02:10:33.999 UTC [491848:5] FATAL: could not create any TCP/IP= sockets 2021-10-14 02:10:34.000 UTC [491848:6] LOG: database system is shut down Bail out! pg_ctl start failed Looks like a transient/phase of the moon issue to me. regards, tom lane