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 1otm9B-00086S-6X for pgsql-general@arkaria.postgresql.org; Sat, 12 Nov 2022 08:45:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1otm8B-0002iH-Ak for pgsql-general@arkaria.postgresql.org; Sat, 12 Nov 2022 08:44:51 +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 1otm8A-0002i8-Td for pgsql-general@lists.postgresql.org; Sat, 12 Nov 2022 08:44:50 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1otm88-0003IM-Bc for pgsql-general@lists.postgresql.org; Sat, 12 Nov 2022 08:44:50 +0000 Received: by mail-oi1-x22c.google.com with SMTP id n186so6948100oih.7 for ; Sat, 12 Nov 2022 00:44:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=B0JC7qzx7JGzd/lQq0YKA3kPWygXEJeinhObxiP3m6A=; b=XJHIJtJcw4b4/FPgLBvVuwEpEZOrOBeJY1hjQ6aDtVlEJMp3K2Nl+w8Aqk8MaHUB0Q 5mvQ93L7C6es5Ce8xREeKfh2ko2WgaCgCEnwlCCJlwaLLJxsednO+dHcSZ8IYvbQKl75 BNwsmCxIhu1Jz4OajsOMpBNFVDty4Glx3kfi/5kasH0b74MXb6N759MOcEmSmes2hDRY 0NQ32ZZEqk/VayxgGCav/r72KfY6P9FbAERRKzelOcvLIB5ZsU3h+IpEN23XoDsI73VJ dsxoEnVia29eNujzXPh+BSOxwX3q5dtSr3uMUqp0AnsCnjo67jGl5QmSFTh8SquLCgMi xLLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=B0JC7qzx7JGzd/lQq0YKA3kPWygXEJeinhObxiP3m6A=; b=1hCg+vXJDUkdu6VW3LzeSEobSURPNF65OkODhcg8aWUrV8Qi/nMFp/G26/izUaiEjh BR08NtL1/q1225KMlQooEBeo3F0RGQH9Ga0b6rkl5PBhkf2cYEzU1M9ZzLA0NKXSIRbs dNrd/2J4rTgXPEQhxsx7AwtbLLdVWUTHCxQQPoMVqYiuRIqjqE0lW9h2FnrsjOPYahxo hGhLj1GhuLmxc7jg2U5wA7hcTijnaq7sMb17Qr959YBl8gn/qZxMqmrTHqb5EXY+ashZ SJnvKtEzYSReMaatd3Logbs7FA4EGdPQIhbGnb8cvOh0OqOfkG0wfNAY98P+Ul/qDWgp eYww== X-Gm-Message-State: ANoB5pk+IFWLEKoZMNBi7O5TnEEH8HELF97Y1Tcjt6ndGyK8jn4IjMvU cRORtaUTdtccBdMQZ5Izx/z2w2kIOQw= X-Google-Smtp-Source: AA0mqf4MJIXm0uUm25cTKTIcrzhQfu/QwmdtriCML6TyfPED9tpyLjRZOA1hVzEh5AdFBVUmzNTD7g== X-Received: by 2002:aca:2202:0:b0:359:bf56:504f with SMTP id b2-20020aca2202000000b00359bf56504fmr2344180oic.139.1668242685349; Sat, 12 Nov 2022 00:44:45 -0800 (PST) Received: from [192.168.88.10] (ip68-230-234-148.no.no.cox.net. [68.230.234.148]) by smtp.googlemail.com with ESMTPSA id x35-20020a05683040a300b0066ca7af5745sm1926984ott.26.2022.11.12.00.44.44 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 12 Nov 2022 00:44:44 -0800 (PST) Content-Type: multipart/alternative; boundary="------------QmKUvJ0aCxgbb10B2ZHLpa0x" Message-ID: <5d2bc34d-ce3a-6e22-59dd-467c441de89d@gmail.com> Date: Sat, 12 Nov 2022 02:44:44 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: Upgrading to v12 Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <9aa1a829-3367-74cf-1630-a91a4d67d41d@aklaver.com> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------QmKUvJ0aCxgbb10B2ZHLpa0x Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Step #1: upgrade to 9.4.26.  You'll get *five years* of bug fixes. (If the client lets you, of course.  I had servers stuck on 8.4.17 and 9.2.7 that were only upgraded because PCI auditors were going to tell my client's client, and that scared /my/ client.  Now they're on 9.6.24...) On 11/11/22 15:42, Brad White wrote: > I'm practicing on our Dev server, so I can blow this away and reload at > any time. > Are there any utilities to check for corruption on my Prod server in v9.4.1? > > All my backups are done with pg_dump.exe, so that's where this database > came from in the first place. > So we know that pg_dump.exe works on Prod at least. > > On Fri, Nov 11, 2022 at 3:17 PM Adrian Klaver > wrote: > > On 11/11/22 13:11, Brad White wrote: > > 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. > > Can you do a pg_dump of that database? > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > -- Angular momentum makes the world go 'round. --------------QmKUvJ0aCxgbb10B2ZHLpa0x Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Step #1: upgrade to 9.4.26.  You'll get five years of bug fixes.

(If the client lets you, of course.  I had servers stuck on 8.4.17 and 9.2.7 that were only upgraded because PCI auditors were going to tell my client's client, and that scared my client.  Now they're on 9.6.24...)

On 11/11/22 15:42, Brad White wrote:
I'm practicing on our Dev server, so I can blow this away and reload at any time.
Are there any utilities to check for corruption on my Prod server in v9.4.1?

All my backups are done with pg_dump.exe, so that's where this database came from in the first place.
So we know that pg_dump.exe works on Prod at least.

On Fri, Nov 11, 2022 at 3:17 PM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 11/11/22 13:11, Brad White wrote:
> 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.

Can you do a pg_dump of that database?


--
Adrian Klaver
adrian.klaver@aklaver.com


--
Angular momentum makes the world go 'round.
--------------QmKUvJ0aCxgbb10B2ZHLpa0x--