From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Odd, intermittent failure in contrib/pageinspect
Date: Mon, 18 Jan 2021 19:40:05 -0300
Message-ID: <20210118224005.GA3146@alvherre.pgsql> (raw)
In-Reply-To: <416195.1611009300@sss.pgh.pa.us>
On 2021-Jan-18, Tom Lane wrote:
> 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.
I guess the machine would have to be pretty constrained. (It takes
almost seven minutes to go through the pg_upgrade test, so it does seems
small.)
> [ thinks for a bit... ] Does the checkpointer pin pages it's writing
> out? I guess it'd have to ...
It does, per SyncOneBuffer(), called from BufferSync(), called from
CheckPointBuffers().
--
Álvaro Herrera 39°49'30"S 73°17'W
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, michael@paquier.xyz, pgsql-hackers@lists.postgresql.org
Subject: Re: Odd, intermittent failure in contrib/pageinspect
In-Reply-To: <20210118224005.GA3146@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox