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 1otbNy-00025m-9b for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 21:16:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1otbNx-0008B8-1V for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 21:16:25 +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 1otbNw-00087q-Mc for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 21:16:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1otbNt-0005CF-Vt for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 21:16:24 +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 2ABLGJcX121079; Fri, 11 Nov 2022 16:16:19 -0500 From: Tom Lane To: Brad White cc: pgsql-general@lists.postgresql.org Subject: Re: Upgrading to v12 In-reply-to: References: Comments: In-reply-to Brad White message dated "Fri, 11 Nov 2022 15:11:29 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <121077.1668201379.1@sss.pgh.pa.us> Date: Fri, 11 Nov 2022 16:16:19 -0500 Message-ID: <121078.1668201379@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Brad White writes: > I deleted all the other DBs and left only the primary. > Still getting the same error message, ending with > ERROR: could not access status of transaction 22316920 > DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error. That's a pretty clear indication of data corruption. pg_upgrade isn't going to be able to work with a corrupted source database, so you'll have to do something to clear that before you can get anywhere. There's some advice about dealing with that here: https://wiki.postgresql.org/wiki/Corruption but in general the news is not going to be good. regards, tom lane