From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Upgrading to v12
Date: Sat, 12 Nov 2022 02:44:44 -0600
Message-ID: <5d2bc34d-ce3a-6e22-59dd-467c441de89d@gmail.com> (raw)
In-Reply-To: <CAA_1=90YFtyBmg-zKZ936H6ke-CmdjjKDS-xTBEfjqpAWxSKUA@mail.gmail.com>
References: <CAA_1=91Vc9a2g4wKNsHoNoMuXDpqQXNhhWq0mRyJMxUAKiEkDQ@mail.gmail.com>
<ec6d3d2e-18f7-db89-c269-b5f28cfe0183@aklaver.com>
<CAA_1=91AU7WaHP-_4mwPVHZVskL6gQOYJ6Tm7VooEhFvtj2_cw@mail.gmail.com>
<CAA_1=93vKW50Ny8kyEtrM=1s8CYU1isFueAOSL+zNpH1Pzzvmg@mail.gmail.com>
<9aa1a829-3367-74cf-1630-a91a4d67d41d@aklaver.com>
<CAA_1=90YFtyBmg-zKZ936H6ke-CmdjjKDS-xTBEfjqpAWxSKUA@mail.gmail.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: Upgrading to v12
In-Reply-To: <5d2bc34d-ce3a-6e22-59dd-467c441de89d@gmail.com>
References: <CAA_1=91Vc9a2g4wKNsHoNoMuXDpqQXNhhWq0mRyJMxUAKiEkDQ@mail.gmail.com> <ec6d3d2e-18f7-db89-c269-b5f28cfe0183@aklaver.com> <CAA_1=91AU7WaHP-_4mwPVHZVskL6gQOYJ6Tm7VooEhFvtj2_cw@mail.gmail.com> <CAA_1=93vKW50Ny8kyEtrM=1s8CYU1isFueAOSL+zNpH1Pzzvmg@mail.gmail.com> <9aa1a829-3367-74cf-1630-a91a4d67d41d@aklaver.com> <CAA_1=90YFtyBmg-zKZ936H6ke-CmdjjKDS-xTBEfjqpAWxSKUA@mail.gmail.com> <5d2bc34d-ce3a-6e22-59dd-467c441de89d@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox