Peter Geoghegan <pg@bowt.ie> writes:
> That was the intent, but that in itself doesn't mean that it isn't
> something to do with setting hint bits (not the OldestXmin horizon
> being held back).
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.
> 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. However, since I've still
utterly failed to reproduce the problem on wrasse's host, I think
we're going to be forced to do that.
regards, tom lane
