| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Running pg_upgrade when changing base platform from rhel 9 to 10. |
| Date: | 2026-09-22 19:09:58 |
| Message-ID: | CANzqJaARAj1gsc7jP42jrUZYN6qQFjuX-Z4LaG2GFfzJm_MKOA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Sep 22, 2026 at 2:34 PM Urvish Rana <urvishrana3728(at)gmail(dot)com>
wrote:
> Hi,
>
> I have a concern of running pg upgrade from pg 16 to pg18. I am also
> changing the base platform from rhel 9 to rhel 10. During my research I
> have found that, pg_upgrade can be run where it has access to both pg
> version’s binaries.
RPMs from the Postgresql.org repository are "multi-version" in that there
are PG16 and PG18 binaries for RHEL10, and you can install them in parallel.
> I also read that after changing platform need to update coalitions for
> index,
Correct. After running the pg18 pg_upgrade, you might need to alter
database and column collations (depending on what collations you use), and
you *will* need to rebuild all indices with text columns.
> as mentioned in Your organization's data cannot be pasted here. Only 20
> characters are allowed.
>
Eh?
> My concern is that I have hugh amount of blob data in my database and
> wanted to understand will changing the platform would affect the data
> consistency?
>
bytea columns should not be affected.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-09-23 05:56:56 | Re: CNPG |
| Previous Message | Urvish Rana | 2026-09-22 18:59:21 | Running pg_upgrade when changing base platform from rhel 9 to 10. |