Re: Running pg_upgrade when changing base platform from rhel 9 to 10.

Thanks Ron for the confirmation.

So, the solution I am going for is to have a container built on rhel9 as
base layer adding pg_16 binaries and on top of that building rhel_10
container and installing pg_18 binaries. I have both binaries available
during run time and database to upgrade.

Regards,

On Tue, Sep 22, 2026 at 3:10 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:

> 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!
>