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 1otcUw-0000HJ-H3 for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 22:27:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1otcUv-0001II-5W for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 22:27:41 +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 1otcUu-0001I8-Qk for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 22:27:40 +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 1otcUq-0001Tf-Op for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 22:27:39 +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 2ABMRY7k128409; Fri, 11 Nov 2022 17:27:35 -0500 From: Tom Lane To: Brad White cc: pgsql-general@lists.postgresql.org Subject: Re: Upgrading to v12 In-reply-to: References: <9aa1a829-3367-74cf-1630-a91a4d67d41d@aklaver.com> Comments: In-reply-to Brad White message dated "Fri, 11 Nov 2022 16:06:31 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <128407.1668205654.1@sss.pgh.pa.us> Date: Fri, 11 Nov 2022 17:27:34 -0500 Message-ID: <128408.1668205654@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Brad White writes: >> Can you do a pg_dump of that database? > Yes. No visible problems. No errors reported. Well, that's quite interesting, because pg_dump ought to read all the same catalogs that pg_upgrade is failing to read. So I'm not quite sure what's going on there. Nonetheless, your path forward is clear: use pg_dump (or better pg_dumpall) and then load the output into a freshly initdb'd v12 installation. It'll be a bit slower than the pg_upgrade way, but it'll work. regards, tom lane