From: garyorban@gmail.com
To: 'Joe Conway' <mail@joeconway.com>
To: pgsql-admin@lists.postgresql.org
Subject: RE: Upgrade Rhel7.9 to Rhel9.3
Date: Wed, 6 Mar 2024 11:48:30 -0500
Message-ID: <190101da6fe6$1edc82a0$5c9587e0$@gmail.com> (raw)
In-Reply-To: <44483f0d-25f2-46e2-8bfb-41fa99d7075e@joeconway.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>
version 12 was installed on this server with rhel7 . Now the server has been upgraded to rhel9.
So do I need to relink the postgres binaries now . If so how do I do that ?
Thanks
Gary
-----Original Message-----
From: Joe Conway <mail@joeconway.com>
Sent: Wednesday, March 6, 2024 11:43 AM
To: garyorban@gmail.com; pgsql-admin@lists.postgresql.org
Subject: Re: Upgrade Rhel7.9 to Rhel9.3
On 3/6/24 11:38, garyorban@gmail.com wrote:
> When we tried on a test server we were seeing issues with
> libcrypto.so.10 and libssl.so.10
>
> I know sometimes symlinks are needed but we can't seem to get these to
> work which led to my question of if postgres12 was supported on
> rhel9.3
How/where are you getting the postgres binaries? They need to be compiled/linked with the libraries on the rhel9 system, and it sounds like you may have built the postgres binaries yourself on rhel7?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
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: garyorban@gmail.com, mail@joeconway.com, pgsql-admin@lists.postgresql.org
Subject: RE: Upgrade Rhel7.9 to Rhel9.3
In-Reply-To: <190101da6fe6$1edc82a0$5c9587e0$@gmail.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