On Fri, Jul 01, 2022 at 06:14:13PM -0500, Justin Pryzby wrote: > I reproduced the problem at 9a974cbcba but not its parent commit. > > commit 9a974cbcba005256a19991203583a94b4f9a21a9 > Author: Robert Haas <rh...@postgresql.org> > Date: Mon Jan 17 13:32:44 2022 -0500 > > pg_upgrade: Preserve relfilenodes and tablespace OIDs.
Oops. Robert? This reproduces as well when using pg_upgrade with the same version as origin and target, meaning that this extra step in the TAP test is able to reproduce the issue (extra VACUUM FULL before chdir'ing): --- a/src/bin/pg_upgrade/t/002_pg_upgrade.pl +++ b/src/bin/pg_upgrade/t/002_pg_upgrade.pl @@ -208,6 +208,8 @@ if (defined($ENV{oldinstall})) } } +$oldnode->safe_psql("regression", "VACUUM FULL pg_largeobject;"); + # In a VPATH build, we'll be started in the source directory, but we want -- Michael
signature.asc
Description: PGP signature