Peter Geoghegan <p...@bowt.ie> writes: > On Sun, May 16, 2021 at 1:23 PM Tom Lane <t...@sss.pgh.pa.us> wrote: >> And the reason oldestXID contains that is that pg_upgrade applied >> pg_resetwal, which does this: >> * For the moment, just set oldestXid to a value that will force >> * immediate autovacuum-for-wraparound.
> This same pg_resetwal code has probably caused quite a few problems on > pg_upgrade'd databases: > https://postgr.es/m/20210423234256.hwopuftipdmp3...@alap3.anarazel.de Hm, yeah. I'm not sure if transferring the value forward from the old cluster is entirely safe, but if it is, that seems like a promising route to a fix. (We should still have more sanity checking around the GlobalVis code, though.) regards, tom lane
