pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: garyorban@gmail.com
To: pgsql-admin@lists.postgresql.org
Subject: Re: Upgrade Rhel7.9 to Rhel9.3
Date: Wed, 6 Mar 2024 17:23:02 -0500
Message-ID: <8bcdedc2-39f2-418b-9fd0-4a0117e41ed9@joeconway.com> (raw)
In-Reply-To: <194001da6fff$5ecd56f0$1c6804d0$@gmail.com>
References: <18e801da6fe3$22ccaff0$68660fd0$@gmail.com>
	<9cc30cb6-7496-4508-bd6f-0640213ed12b@joeconway.com>
	<18f701da6fe4$ac2fc790$048f56b0$@gmail.com>
	<44483f0d-25f2-46e2-8bfb-41fa99d7075e@joeconway.com>
	<190101da6fe6$1edc82a0$5c9587e0$@gmail.com>
	<8386b391-12b7-4852-8b5a-b8489cec7643@joeconway.com>
	<194001da6fff$5ecd56f0$1c6804d0$@gmail.com>

On 3/6/24 14:49, garyorban@gmail.com wrote:
> Appreciate the help. The person who performed the original upgrades
> in no longer with us. I believe they used an RPM for that install .
> 
> I was able to get postgres 12 to start on rhel 9.3 with the following
> tweaks.
> 
> Copied over libcrypto, libssl , libreadline and libtinfo  from
> another  rhel 7 server. Also needed symlinks for libicuil8n and
> libicuuc .
> 
> I was able to access the DB and perform simple queries . Do you think
> this approach will work, as I'm a bit leery . If not what do you
> think would be a better option?

Yeah, it can be done like that but it sounds a bit sketchy and would 
make me nervous.

I would recommend installing the rhel9  binaries from RPMs instead.
See https://yum.postgresql.org/ for the Postgres community curated repo, 
for example.

As long as the rhel9 new binaries are the same architecture (e.g. 
x86_64) and major version (e.g. 12.18), they should "just work" with 
your existing data directory.

Although that said, as I mentioned in my first response, indexes built 
on collatable columns most likely need to be rebuilt due to the newer 
version of glibc on the rhel9 system. The rebuilds should be done 
*before* allowing any "writes" (inserts or updates) to the new instance. 
Other potential collation issues as illustrated in the presentation I 
linked should also be considered, e.g. partition keys.

Overall, it sounds to me like you should get a consulting/support 
company to help you with this. See: 
https://www.postgresql.org/support/professional_support/

Hope this helps,

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com






view thread (10+ messages)

Message-ID: <8bcdedc2-39f2-418b-9fd0-4a0117e41ed9@joeconway.com>
Permalink:  ../8bcdedc2-39f2-418b-9fd0-4a0117e41ed9@joeconway.com/
Also on:    postgresql.org/message-id/8bcdedc2-39f2-418b-9fd0-4a0117e41ed9@joeconway.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: mail@joeconway.com, garyorban@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Upgrade Rhel7.9 to Rhel9.3
  In-Reply-To: <8bcdedc2-39f2-418b-9fd0-4a0117e41ed9@joeconway.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox