| From: | Sameer Malve <malvesameer(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Zaid Shabbir <zaidshabbir(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org, Sameer(dot)Malve(at)mobileum(dot)com, purav(dot)chovatia(at)mobileum(dot)com |
| Subject: | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |
| Date: | 2024-10-08 11:20:58 |
| Message-ID: | CAEGp0djRTqRvomPfyem0YGbzjDLSiDjDaob3FPYqTbg-G-T-9g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
+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 | Scott Ribe | 2024-10-08 12:28:55 | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |
| Previous Message | Laurenz Albe | 2024-10-08 10:48:24 | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |