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 1l1d78-0006K0-U8 for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2021 22:35:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l1d77-0005oe-L0 for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2021 22:35:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l1d77-0005oX-EG for pgsql-hackers@lists.postgresql.org; Mon, 18 Jan 2021 22:35:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l1d72-0006jl-Vx for pgsql-hackers@lists.postgresql.org; Mon, 18 Jan 2021 22:35:09 +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 10IMZ0KX416196; Mon, 18 Jan 2021 17:35:00 -0500 From: Tom Lane To: Alvaro Herrera cc: Michael Paquier , pgsql-hackers@lists.postgresql.org Subject: Re: Odd, intermittent failure in contrib/pageinspect In-reply-to: <20210118223019.GA2579@alvherre.pgsql> References: <20210118223019.GA2579@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Mon, 18 Jan 2021 19:30:19 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <416194.1611009300.1@sss.pgh.pa.us> Date: Mon, 18 Jan 2021 17:35:00 -0500 Message-ID: <416195.1611009300@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2021-Jan-18, Tom Lane wrote: >> Searching the buildfarm logs turned up exactly one previous occurrence, >> also on whelk [2]. So I'm not sure what to make of it. Could the >> immediately preceding VACUUM FREEZE command have silently skipped this >> page for some reason? That'd be a bug I should think. > Hmm, doesn't vacuum skip pages when they are pinned? I don't think > VACUUM FREEZE would be treated especially -- only "aggressive" > wraparound would be an exception, IIRC. Right. If that's the explanation, then adding DISABLE_PAGE_SKIPPING to the test's VACUUM options should fix it. However, to believe that theory you have to have some reason to think that some other process might have the page pinned. What would that be? test1 only has one small tuple in it, so it doesn't seem credible that autovacuum or autoanalyze would have fired on it. [ thinks for a bit... ] Does the checkpointer pin pages it's writing out? I guess it'd have to ... regards, tom lane