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 1oHZDq-0004fi-KV for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Jul 2022 23:16:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oHZDo-0000uz-D9 for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Jul 2022 23:16:44 +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 1oHZDo-0000up-3c for pgsql-hackers@lists.postgresql.org; Fri, 29 Jul 2022 23:16:44 +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 1oHZDl-0003Ye-DG for pgsql-hackers@postgresql.org; Fri, 29 Jul 2022 23:16:42 +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 26TNGYKx125445; Fri, 29 Jul 2022 19:16:34 -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> Comments: In-reply-to Robert Haas message dated "Fri, 29 Jul 2022 18:28:44 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <125443.1659136594.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 29 Jul 2022 19:16:34 -0400 Message-ID: <125444.1659136594@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > wrasse just failed the new test: > [00:09:44.167](0.001s) not ok 16 - old and new horizons match after pg_u= pgrade > [00:09:44.167](0.001s) > [00:09:44.167](0.000s) # Failed test 'old and new horizons match > after pg_upgrade' > # at t/002_pg_upgrade.pl line 345. > [00:09:44.168](0.000s) # got: '1' > # expected: '0' > =3D=3D=3D diff of /export/home/nm/farm/studio64v12_6/HEAD/pgsql.build/sr= c/bin/pg_upgrade/tmp_check/tmp_test_D3cJ/horizon1.txt > and /export/home/nm/farm/studio64v12_6/HEAD/pgsql.build/src/bin/pg_upgra= de/tmp_check/tmp_test_D3cJ/horizon2.txt > =3D=3D=3D stdout =3D=3D=3D > 1c1 > < pg_backend_pid|21767 > --- > > pg_backend_pid|22045=3D=3D=3D stderr =3D=3D=3D > =3D=3D=3D EOF =3D=3D=3D > I'm slightly befuddled as to how we're ending up with a table named > pg_backend_pid. That's not the only thing weird about this printout: there should be three columns not two in that query's output, and what happened to the trailing newline? I don't think we're looking at desired output at all. I am suspicious that the problem stems from the nonstandard way you've invoked psql to collect the horizon data. At the very least this code is duplicating bits of Cluster::psql that it'd be better not to; and I wonder if the issue is that it's not duplicating enough. The lack of -X and the lack of use of installed_command() are red flags. Do you really need to do it like this? regards, tom lane