From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Intermittent buildfarm failures on wrasse |
Date: | 2022-04-15 02:27:26 |
Message-ID: | CAH2-Wz=V=cd9wO+96_1htgjY6TrT6OF7BzR8W+vuPZMAwnUF4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 14, 2022 at 7:20 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Oh! You mean that maybe the OldestXmin horizon was fine, but something
> decided not to update hint bits (and therefore also not the all-visible
> bit) anyway? Worth investigating I guess.
Yes. That is starting to seem like a plausible alternative explanation.
> > I'd really like to know what the removable cutoff
> > looks like for these VACUUM operations, which is something like
> > Andres' VACUUM VERBOSE debug patch should tell us.
>
> Yeah. I'd hoped to investigate this manually and not have to clutter
> the main repo with debugging commits.
Suppose that the bug was actually in 06f5295af6, "Add single-item
cache when looking at topmost XID of a subtrans XID". Doesn't that fit
your timeline just as well?
I haven't really started to investigate that theory (just putting
dinner on here). Just a wild guess at this point.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-15 02:40:51 | Re: Intermittent buildfarm failures on wrasse |
Previous Message | Tom Lane | 2022-04-15 02:20:29 | Re: Intermittent buildfarm failures on wrasse |