Re: Odd, intermittent failure in contrib/pageinspect
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers@lists.postgresql.org
Date: 2021-01-18T22:35:00Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> 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
Commits
-
Disable vacuum page skipping in selected test cases.
- c2dc1a79767a 14.0 landed
- a57dbfcda553 13.2 landed
- 6a97ca31288d 11.11 landed
- 53a24faaa403 12.6 landed
- 3ae247d40231 10.16 landed