Re: Intermittent buildfarm failures on wrasse - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Intermittent buildfarm failures on wrasse
Date
Msg-id 1486022.1649952083@sss.pgh.pa.us
Whole thread Raw
In response to Re: Intermittent buildfarm failures on wrasse  (Noah Misch <noah@leadboat.com>)
Responses Re: Intermittent buildfarm failures on wrasse
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> On Wed, Apr 13, 2022 at 06:51:12PM -0700, Andres Freund wrote:
>> Noah, any chance you could enable log_autovacuum_min_duration=0 on
>> wrasse?

> Done.  Also forced hourly builds.

Thanks!  We now have two failing runs with the additional info [1][2],
and in both, it's clear that the first autovac worker doesn't launch
until 1 minute after postmaster start, by which time we're long done
with the test scripts of interest.  So whatever is breaking this is
not an autovac worker.

I think I'm going to temporarily add a couple of queries to check
what tenk1's relallvisible actually is, just so we can confirm
positively that that's what's causing the plan change.  (I'm also
curious about whether the CREATE INDEX steps manage to change it
at all.)

            regards, tom lane

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2022-04-14%2013%3A28%3A14
[2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2022-04-14%2004%3A48%3A13



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: TRAP: FailedAssertion("HaveRegisteredOrActiveSnapshot()", File: "toast_internals.c", Line: 670, PID: 19403)
Next
From: Nathan Bossart
Date:
Subject: Re: allow specifying action when standby encounters incompatible parameter settings