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 1oLEPa-0001Uk-AA for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Aug 2022 01:52:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oLEPX-0002lD-Te for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Aug 2022 01:51:59 +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 1oLEPX-0002l4-FT for pgsql-hackers@lists.postgresql.org; Tue, 09 Aug 2022 01:51:59 +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 1oLEPQ-0006tk-Ry; Tue, 09 Aug 2022 01:51:58 +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 2791pkWd758597; Mon, 8 Aug 2022 21:51:46 -0400 From: Tom Lane To: Bruce Momjian cc: "Jonathan S. Katz" , Noah Misch , Robert Haas , Andrew Dunstan , Michael Paquier , Justin Pryzby , "pgsql-hackers@postgresql.org" , Shruthi Gowda Subject: Re: pg15b2: large objects lost on upgrade In-reply-to: References: <4152163.1659124804@sss.pgh.pa.us> <125444.1659136594@sss.pgh.pa.us> <20220730054401.GB3644221@rfd.leadboat.com> <351616.1659192034@sss.pgh.pa.us> <635c8809-3525-7dae-a1a1-0d9069cd86bc@postgresql.org> <2657259.1659460333@sss.pgh.pa.us> <2684751.1659468725@sss.pgh.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 08 Aug 2022 20:59:29 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <758595.1660009906.1@sss.pgh.pa.us> Date: Mon, 08 Aug 2022 21:51:46 -0400 Message-ID: <758596.1660009906@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bruce Momjian writes: >> Hmmm ... now that you mention it, I see nothing in 002_pg_upgrade.pl >> that attempts to turn off autovacuum on either the source server or >> the destination. So one plausible theory is that autovac moved the >> numbers since we checked. > Uh, pg_upgrade assumes autovacuum is not running, and tries to enforce > this: The problems come from autovac running before or after pg_upgrade. > Perhaps the test script should do something similar, I'm not on board with that, for the reasons I gave upthread. regards, tom lane