Thread: RHEL certified repo provided PostgreSQL Major Version Upgrade.

Hi Team,

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.

pg_upgrade command is as follows.

[2024-10-04 11:18:47]  $ /usr/bin/pg_upgrade -b /usr/bin/ -B /usr/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c
[2024-10-04 11:19:19]  
[2024-10-04 11:19:19]  You must identify the directory where the old cluster binaries reside.
[2024-10-04 11:19:19]  Please use the -b command-line option or the PGBINOLD environment variable.
[2024-10-04 11:19:19]  Failure, exiting

 

Regards,

Sameer Malve

Hi Team,

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.

pg_upgrade command is as follows.

[2024-10-04 11:18:47]  $ /usr/bin/pg_upgrade -b /usr/bin/ -B /usr/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c
[2024-10-04 11:19:19]  
[2024-10-04 11:19:19]  You must identify the directory where the old cluster binaries reside.
[2024-10-04 11:19:19]  Please use the -b command-line option or the PGBINOLD environment variable.
[2024-10-04 11:19:19]  Failure, exiting

 

Regards,

Sameer Malve

Hi Sameer,

Please try with this command.

/usr/bin/pg_upgrade -b /usr/pgsql-15/bin/ -B /usr/pgsql-16/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c

If above command is not working check the below one.

/usr/pgsql-16/bin/pg_upgrade -b /usr/pgsql-15/bin/ -B /usr/pgsql-16/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c

Thanks & Regards

Obireddy

On Tue, 8 Oct 2024, 13:54 Sameer Malve, <malvesameer@gmail.com> wrote:

Hi Team,

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.

pg_upgrade command is as follows.

[2024-10-04 11:18:47]  $ /usr/bin/pg_upgrade -b /usr/bin/ -B /usr/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c
[2024-10-04 11:19:19]  
[2024-10-04 11:19:19]  You must identify the directory where the old cluster binaries reside.
[2024-10-04 11:19:19]  Please use the -b command-line option or the PGBINOLD environment variable.
[2024-10-04 11:19:19]  Failure, exiting

 

Regards,

Sameer Malve

Hello Sameer,

For upgrade you can also use quick upgrade scripts

/usr/pgsql-16/bin/postgresql-16-setup check_upgrade

/usr/pgsql-16/bin/postgresql-16-setup upgrade

Above commands are helpful to upgrade from 15 to 16, in case someone wants to upgrade from -2 older version then some minor adjustments required in setup script.

Regards,

Zaid

On Tue, Oct 8, 2024 at 1:24 PM Sameer Malve <malvesameer@gmail.com> wrote:

Hi Team,

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.

pg_upgrade command is as follows.

[2024-10-04 11:18:47]  $ /usr/bin/pg_upgrade -b /usr/bin/ -B /usr/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c
[2024-10-04 11:19:19]  
[2024-10-04 11:19:19]  You must identify the directory where the old cluster binaries reside.
[2024-10-04 11:19:19]  Please use the -b command-line option or the PGBINOLD environment variable.
[2024-10-04 11:19:19]  Failure, exiting

 

Regards,

Sameer Malve

On Tue, 2024-10-08 at 16:03 +0530, Sameer Malve wrote:
[about pg_upgrade]
> Does this Upgrade command stand true in case of postgres upgrade between community (PGDG) to RHEL?

Probably, unless they configured something differently that affects
the storage format.  Try and see.

Recommendation: keep using PGDG packages.

Yours,
Laurenz Albe

+purav.chovatia@mobileum.com 

Hi Laurenz ,

We have installed the PostgreSQL from RHEL repo using `dnf install <package name>` so we have not passed any customised path for installation.

And there the problem arises as older version binaries get overwritten when we upgrade/ install the new version of Postgres.  

Regards,

Sameer Malve

On Tue, Oct 8, 2024 at 4:18 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:

On Tue, 2024-10-08 at 16:03 +0530, Sameer Malve wrote:
[about pg_upgrade]
> Does this Upgrade command stand true in case of postgres upgrade between community (PGDG) to RHEL?

Probably, unless they configured something differently that affects
the storage format.  Try and see.

Recommendation: keep using PGDG packages.

Yours,
Laurenz Albe

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

---

From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Tuesday, October 8, 2024 7:15:49 PM
To: Sameer Malve <malvesameer@gmail.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>; Sameer Malve <Sameer.Malve@mobileum.com>
Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.

 

Caution :External

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