public inbox for [email protected]
help / color / mirror / Atom feedFrom: Sameer Malve <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected] <[email protected]>
Cc: Sameer Malve <[email protected]>
Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
Date: Thu, 10 Oct 2024 11:52:47 +0530
Message-ID: <CAEGp0dg7cm0E3AUNhOnEGNM2TYr3KDg8iqRMpRWu16zVmaTqpQ@mail.gmail.com> (raw)
In-Reply-To: <PH0PR14MB520943781088094A05AA3244FD7E2@PH0PR14MB5209.namprd14.prod.outlook.com>
References: <CAEGp0dgUL=j4ULDfGz4j=kbv2sAzP5dmp=Wem7cOknq8gyge4Q@mail.gmail.com>
<[email protected]>
<PH0PR14MB520943781088094A05AA3244FD7E2@PH0PR14MB5209.namprd14.prod.outlook.com>
Hi Tom,
Thanks for providing me with the correct point to look for a solution, and
I was able to upgrade my cluster from PG15.6 to PG 16.4.
I have few questions.
1. As I have observed, the PostgreSQL upgrade package has only the lower
major version binaries. So what if I want to upgrade from PG 13 to PG 16?
2. If upgrade fails then what are the rollback steps. Do you know if it is
documented somewhere?
Regards,
Sameer Malve
On Tue, Oct 8, 2024 at 7:32 PM Sameer Malve <[email protected]>
wrote:
> Thanks Tom. I have installed that upgrade package rpm will go through it
> and try. And would let you know incase I get stucked .
>
> Get Outlook for Android <https://aka.ms/AAb9ysg;
> ------------------------------
> *From:* Tom Lane <[email protected]>
> *Sent:* Tuesday, October 8, 2024 7:15:49 PM
> *To:* Sameer Malve <[email protected]>
> *Cc:* [email protected] <[email protected]>;
> Sameer Malve <[email protected]>
> *Subject:* Re: RHEL certified repo provided PostgreSQL Major Version
> Upgrade.
>
> Caution :External
>
> Sameer Malve <[email protected]> writes:
> > We are trying to perform the Major version upgrade on RHEL 8 using
> > RHEL-certified repo `rhel-8-for-x86_64-appstream-rpms` from PG 15.6 to PG
> > 16.4 using `pg_upgrade` but we are facing the below issue.
> > As the binaries are getting upgraded in-place `/usr/bin` hence while
> > performing pg_upgrade we are not getting the older binaries.
>
> It's been more than ten years since I was responsible for Red Hat's
> packaging of PG, but I think I recall that the solution in place for
> pg_upgrade involved a separate postgresql-upgrade RPM containing
> previous-version executables, which you were supposed to install
> alongside the new version for long enough to perform the upgrade.
> Whatever the details were, I'm quite certain the package's README file
> contained an explanation of how to do it. Read that, do not pay
> attention to people or chatbots telling you how you'd do it with some
> other packaging.
>
> regards, tom lane
>
view thread (13+ messages) latest in thread
reply
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
In-Reply-To: <CAEGp0dg7cm0E3AUNhOnEGNM2TYr3KDg8iqRMpRWu16zVmaTqpQ@mail.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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox