From: | Holger Jakobs <holger(at)jakobs(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |
Date: | 2024-10-08 14:20:10 |
Message-ID: | DB4856E6-B207-4A0F-AF89-9BD08201706A@jakobs.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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 <malvesameer(at)gmail(dot)com>:
>+purav(dot)chovatia(at)mobileum(dot)com <purav(dot)chovatia(at)mobileum(dot)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(dot)albe(at)cybertec(dot)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
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Sameer Malve | 2024-10-10 06:22:47 | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |
Previous Message | Sameer Malve | 2024-10-08 14:02:00 | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |