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 1lJ260-00045W-P8 for pgsql-hackers@arkaria.postgresql.org; Sun, 07 Mar 2021 22:41:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lJ25y-0001RY-Dl for pgsql-hackers@arkaria.postgresql.org; Sun, 07 Mar 2021 22:41:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lJ25y-0001RQ-6k for pgsql-hackers@lists.postgresql.org; Sun, 07 Mar 2021 22:41:54 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lJ25r-0000vz-Cy for pgsql-hackers@postgresql.org; Sun, 07 Mar 2021 22:41:53 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id A8CD81A95F25 for ; Sun, 7 Mar 2021 23:41:44 +0100 (CET) Received: from s630.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 8AD3F2E682E1; Sun, 7 Mar 2021 23:41:44 +0100 (CET) Received: from s470.loopia.se (unknown [172.22.191.5]) by s630.loopia.se (Postfix) with ESMTP id 7FCE313ABE22; Sun, 7 Mar 2021 23:41:44 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s500.loopia.se ([172.22.191.5]) by s470.loopia.se (s470.loopia.se [172.22.190.10]) (amavisd-new, port 10024) with LMTP id 0krNxuBjBoRH; Sun, 7 Mar 2021 23:41:43 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from [192.168.72.43] (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s500.loopia.se (Postfix) with ESMTPSA id B0CDF1E32D06; Sun, 7 Mar 2021 23:41:43 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Subject: Re: pg_upgrade failing for 200+ million Large Objects From: Daniel Gustafsson In-Reply-To: <2543eda3e609455e9cf283646a8b2bc8@EX13D05UWC001.ant.amazon.com> Date: Sun, 7 Mar 2021 23:41:42 +0100 Cc: "pgsql-hackers@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <2543eda3e609455e9cf283646a8b2bc8@EX13D05UWC001.ant.amazon.com> To: "Tharakan, Robins" X-Mailer: Apple Mail (2.3445.104.17) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 7 Mar 2021, at 09:43, Tharakan, Robins wrote: > The patch (attached): > - Applies cleanly on REL9_6_STABLE - > c7a4fc3dd001646d5938687ad59ab84545d5d043 Did you target 9.6 because that's where you want to upgrade to, or is = this not a problem on HEAD? If it's still a problem on HEAD you should probably = submit the patch against there. You probably also want to add it to the next = commit fest to make sure it's not forgotten about: = https://commitfest.postgresql.org/33/ > I am not married to the patch (especially the argument name) but = ideally I'd > prefer a way to get this upgrade going without a patch. For now, I am = unable > to find any other way to upgrade a v9.5 Postgres database in this = scenario, > facing End-of-Life. It's obviously not my call to make in any shape or form, but this = doesn't really seem to fall under what is generally backported into a stable = release? -- Daniel Gustafsson https://vmware.com/=