Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHZwe-0000LE-VP for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Jul 2022 00:03:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oHZwd-0007nS-6K for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Jul 2022 00:03:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHZwc-0007mO-Sb for pgsql-hackers@lists.postgresql.org; Sat, 30 Jul 2022 00:03:02 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHZwW-0003vU-JD for pgsql-hackers@postgresql.org; Sat, 30 Jul 2022 00:03:01 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 26U02pQw135635; Fri, 29 Jul 2022 20:02:51 -0400 From: Tom Lane To: Robert Haas cc: Noah Misch , Andrew Dunstan , Bruce Momjian , Michael Paquier , Justin Pryzby , "pgsql-hackers@postgresql.org" , Shruthi Gowda Subject: Re: pg15b2: large objects lost on upgrade In-reply-to: References: <20220702154917.GM13040@telsasoft.com> <3901843.1659116952@sss.pgh.pa.us> <4152163.1659124804@sss.pgh.pa.us> <125444.1659136594@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Fri, 29 Jul 2022 19:36:14 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <135633.1659139371.1@sss.pgh.pa.us> Date: Fri, 29 Jul 2022 20:02:51 -0400 Message-ID: <135634.1659139371@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > On Fri, Jul 29, 2022 at 7:16 PM Tom Lane wrote: >> I am suspicious that the problem stems from the nonstandard >> way you've invoked psql to collect the horizon data. > Well, I just copied the pg_dump block which occurs directly beforehand > and modified it. I think that must take care of setting the path > properly, else we'd have things blowing up all over the place. But the > lack of -X could be an issue. Hmm. Now that I look, I do see two pre-existing "naked" invocations of psql in 002_pg_upgrade.pl, ie $oldnode->command_ok([ 'psql', '-X', '-f', $olddumpfile, 'postgres' ], 'loaded old dump file'); $oldnode->command_ok( [ 'psql', '-X', '-f', "$srcdir/src/bin/pg_upgrade/upgrade_adapt.sql", 'regression' ], 'ran adapt script'); Those suggest that maybe all you need is -X. However, I don't think either of those calls is reached by the majority of buildfarm animals, only ones that are doing cross-version-upgrade tests. So there could be more secret sauce needed to get this to pass everywhere. Personally I'd try to replace the two horizon-collection steps with $newnode->psql calls, using extra_params to inject the '-o' and target filename command line words. But if you want to try adding -X as a quicker answer, maybe that will be enough. regards, tom lane