From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sameer Malve <malvesameer@gmail.com>
cc: pgsql-admin@lists.postgresql.org, Sameer.Malve@mobileum.com
Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
In-reply-to: 
 <CAEGp0dgUL=j4ULDfGz4j=kbv2sAzP5dmp=Wem7cOknq8gyge4Q@mail.gmail.com>
References: 
 <CAEGp0dgUL=j4ULDfGz4j=kbv2sAzP5dmp=Wem7cOknq8gyge4Q@mail.gmail.com>
Comments: In-reply-to Sameer Malve <malvesameer@gmail.com>
	message dated "Tue, 08 Oct 2024 13:54:11 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1910787.1728395149.1@sss.pgh.pa.us>
Date: Tue, 08 Oct 2024 09:45:49 -0400
Message-ID: <1910788.1728395149@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1910788.1728395149%40sss.pgh.pa.us>
Precedence: bulk

Sameer Malve <malvesameer@gmail.com> 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