public inbox for [email protected]
help / color / mirror / Atom feedRHEL certified repo provided PostgreSQL Major Version Upgrade.
13+ messages / 8 participants
[nested] [flat]
* RHEL certified repo provided PostgreSQL Major Version Upgrade.
@ 2024-10-08 08:24 Sameer Malve <[email protected]>
2024-10-08 08:32 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. obi reddy <[email protected]>
2024-10-08 09:54 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Zaid Shabbir <[email protected]>
2024-10-08 13:45 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Tom Lane <[email protected]>
0 siblings, 3 replies; 13+ messages in thread
From: Sameer Malve @ 2024-10-08 08:24 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
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
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-08 08:32 ` obi reddy <[email protected]>
2024-10-08 10:25 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2 siblings, 1 reply; 13+ messages in thread
From: obi reddy @ 2024-10-08 08:32 UTC (permalink / raw)
To: Sameer Malve <[email protected]>; +Cc: pgsql-admin <[email protected]>; [email protected]
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, <[email protected]> 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
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 08:32 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. obi reddy <[email protected]>
@ 2024-10-08 10:25 ` Sameer Malve <[email protected]>
0 siblings, 0 replies; 13+ messages in thread
From: Sameer Malve @ 2024-10-08 10:25 UTC (permalink / raw)
To: obi reddy <[email protected]>; +Cc: pgsql-admin <[email protected]>; [email protected]
Hi Obi,
Just to update you, we are not using the PGDG community that provides
Postgres.
And the major difference between the PGDG community provided Postgres and
RHEL provided Postgres is the binary files are installed in different
location.
in PGDG Postgres it is installed under `/usr/pgsql-16/bin` whereas in RHEL
Postgres it gets installed under `/usr/bin`.
hence we can't use the command you suggested.
Regards,
Sameer Malve.
On Tue, Oct 8, 2024 at 2:02 PM obi reddy <[email protected]> wrote:
> 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, <[email protected]> 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
>>
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-08 09:54 ` Zaid Shabbir <[email protected]>
2024-10-08 10:33 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2 siblings, 1 reply; 13+ messages in thread
From: Zaid Shabbir @ 2024-10-08 09:54 UTC (permalink / raw)
To: Sameer Malve <[email protected]>; +Cc: [email protected]; [email protected]
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 <[email protected]> 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
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 09:54 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Zaid Shabbir <[email protected]>
@ 2024-10-08 10:33 ` Sameer Malve <[email protected]>
2024-10-08 10:48 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Laurenz Albe <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Sameer Malve @ 2024-10-08 10:33 UTC (permalink / raw)
To: Zaid Shabbir <[email protected]>; +Cc: [email protected]; [email protected]
Hi Zaid,
Does this Upgrade command stand true in case of postgres upgrade between
community (PGDG) to RHEL?
Regards,
Sameer Malve
On Tue, Oct 8, 2024 at 3:24 PM Zaid Shabbir <[email protected]> wrote:
> 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 <[email protected]> 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
>>
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 09:54 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Zaid Shabbir <[email protected]>
2024-10-08 10:33 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-08 10:48 ` Laurenz Albe <[email protected]>
2024-10-08 11:20 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Laurenz Albe @ 2024-10-08 10:48 UTC (permalink / raw)
To: Sameer Malve <[email protected]>; Zaid Shabbir <[email protected]>; +Cc: [email protected]; [email protected]
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
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 09:54 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Zaid Shabbir <[email protected]>
2024-10-08 10:33 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 10:48 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Laurenz Albe <[email protected]>
@ 2024-10-08 11:20 ` Sameer Malve <[email protected]>
2024-10-08 12:28 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Scott Ribe <[email protected]>
2024-10-08 14:20 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Holger Jakobs <[email protected]>
0 siblings, 2 replies; 13+ messages in thread
From: Sameer Malve @ 2024-10-08 11:20 UTC (permalink / raw)
To: Laurenz Albe <[email protected]>; +Cc: Zaid Shabbir <[email protected]>; [email protected]; [email protected]; [email protected]
[email protected] <[email protected]>
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 <[email protected]>
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
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 09:54 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Zaid Shabbir <[email protected]>
2024-10-08 10:33 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 10:48 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Laurenz Albe <[email protected]>
2024-10-08 11:20 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-08 12:28 ` Scott Ribe <[email protected]>
1 sibling, 0 replies; 13+ messages in thread
From: Scott Ribe @ 2024-10-08 12:28 UTC (permalink / raw)
To: Sameer Malve <[email protected]>; +Cc: Pgsql-admin <[email protected]>
> On Oct 8, 2024, at 5:20 AM, Sameer Malve <[email protected]> wrote:
>
> And there the problem arises as older version binaries get overwritten when we upgrade/ install the new version of Postgres.
Install the older version and proceed. (Although first I'd make sure that the PG in /usr/bin is not a symlink.)
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 09:54 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Zaid Shabbir <[email protected]>
2024-10-08 10:33 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 10:48 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Laurenz Albe <[email protected]>
2024-10-08 11:20 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-08 14:20 ` Holger Jakobs <[email protected]>
1 sibling, 0 replies; 13+ messages in thread
From: Holger Jakobs @ 2024-10-08 14:20 UTC (permalink / raw)
To: [email protected]
Before installing the new version over the old one, save the binaries and libraries to another path. You can later provide this path to pg_upgrade.
After successful upgrade, delete the saved old files.
Regards
Holger
--
Holger Jakobs, Bergisch Gladbach
Tel. +49 178 9759012
Am 8. Oktober 2024 13:20:58 MESZ schrieb Sameer Malve <[email protected]>:
>[email protected] <[email protected]>
>
>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 <[email protected]>
>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
>>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-08 13:45 ` Tom Lane <[email protected]>
2024-10-08 14:02 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2 siblings, 1 reply; 13+ messages in thread
From: Tom Lane @ 2024-10-08 13:45 UTC (permalink / raw)
To: Sameer Malve <[email protected]>; +Cc: [email protected]; [email protected]
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
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 13:45 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Tom Lane <[email protected]>
@ 2024-10-08 14:02 ` Sameer Malve <[email protected]>
2024-10-10 06:22 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Sameer Malve @ 2024-10-08 14:02 UTC (permalink / raw)
To: Tom Lane <[email protected]>; Sameer Malve <[email protected]>; +Cc: [email protected] <[email protected]>
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
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 13:45 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Tom Lane <[email protected]>
2024-10-08 14:02 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-10 06:22 ` Sameer Malve <[email protected]>
2024-10-10 06:33 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Laurenz Albe <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Sameer Malve @ 2024-10-10 06:22 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: [email protected] <[email protected]>; Sameer Malve <[email protected]>
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
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: RHEL certified repo provided PostgreSQL Major Version Upgrade.
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 13:45 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Tom Lane <[email protected]>
2024-10-08 14:02 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-10 06:22 ` Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
@ 2024-10-10 06:33 ` Laurenz Albe <[email protected]>
0 siblings, 0 replies; 13+ messages in thread
From: Laurenz Albe @ 2024-10-10 06:33 UTC (permalink / raw)
To: Sameer Malve <[email protected]>; Tom Lane <[email protected]>; +Cc: [email protected] <[email protected]>; Sameer Malve <[email protected]>
On Thu, 2024-10-10 at 11:52 +0530, Sameer Malve wrote:
> 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?
That works just the same.
> 2. If upgrade fails then what are the rollback steps. Do you know if it is documented somewhere?
If you didn't use the --link option of pg_upgrade, you can simply fall back to
the old cluster.
If you used --link, you will have to restore your backup (or promote a standby
server that you prepared for this eventuality).
See the pg_upgrade documentation.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 13+ messages in thread
end of thread, other threads:[~2024-10-10 06:33 UTC | newest]
Thread overview: 13+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-10-08 08:24 RHEL certified repo provided PostgreSQL Major Version Upgrade. Sameer Malve <[email protected]>
2024-10-08 08:32 ` obi reddy <[email protected]>
2024-10-08 10:25 ` Sameer Malve <[email protected]>
2024-10-08 09:54 ` Zaid Shabbir <[email protected]>
2024-10-08 10:33 ` Sameer Malve <[email protected]>
2024-10-08 10:48 ` Laurenz Albe <[email protected]>
2024-10-08 11:20 ` Sameer Malve <[email protected]>
2024-10-08 12:28 ` Scott Ribe <[email protected]>
2024-10-08 14:20 ` Holger Jakobs <[email protected]>
2024-10-08 13:45 ` Tom Lane <[email protected]>
2024-10-08 14:02 ` Sameer Malve <[email protected]>
2024-10-10 06:22 ` Sameer Malve <[email protected]>
2024-10-10 06:33 ` Laurenz Albe <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox