Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qRDlK-000wj5-8R for pgsql-general@arkaria.postgresql.org; Wed, 02 Aug 2023 15:27:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qRDlI-005tsc-Nf for pgsql-general@arkaria.postgresql.org; Wed, 02 Aug 2023 15:27:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qRDlI-005tsS-CE for pgsql-general@lists.postgresql.org; Wed, 02 Aug 2023 15:27:44 +0000 Received: from mrw-2.mail.tiscali.it ([195.130.225.202]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qRDlF-0009Wk-OS for pgsql-general@postgresql.org; Wed, 02 Aug 2023 15:27:43 +0000 Received: from [10.39.80.30] by mrw-2 with esmtp (Exim) id 1qRDlC-006MDX-Ox; Wed, 02 Aug 2023 15:27:39 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tiscali.it; s=mail; h=Message-ID:References:In-Reply-To:Subject:To:From:Date: Content-Type:MIME-Version:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=4xHqIA0IgSw/BpoKjUkR4oidy+jm7pBsVvI4zEY8VWk=; b=GsCQCn6v/hAg45XyjjUYyRhwuV 086ngBws+cgpsZBXU6kTSpFr5PCqaMYXrt8uMYKexdAgoXD7mrA1lF5uK1Nr6KWumBcrdJwOfqGhf wrupeMIlRayr8YC8/pJpun1VSMqeLGdv79LXUM3Kav2AUk4hOXMlY4emf/Ztzfulu1ho=; Received: from rc-14.mc.tiscali.sys ([10.39.75.134]:45521 helo=mail.tiscali.it) by mrl-2.mail.tiscali.sys with esmtp (Exim 4.89) (envelope-from ) id 1qRDlA-00GcJy-OH for pgsql-general@postgresql.org; Wed, 02 Aug 2023 15:27:36 +0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_9d5e954cf632b9ea0aebb6896bb0feec" Date: Wed, 02 Aug 2023 17:27:35 +0200 From: marco.ptz@tiscali.it To: Subject: Re: Different releases in the same server In-Reply-To: References: <7229c9037c2b263c23b4a9d48d7732a2@tiscali.it> Message-ID: <5f5a6b6774e74f76404a433e4e369232@tiscali.it> X-Sender: marco.ptz@tiscali.it X-Originating-IP: 151.56.1.160 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_9d5e954cf632b9ea0aebb6896bb0feec Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8 Hi Christoph, thank you very much for your time. We know the 2 releases are old, unfortunately we cannot change requirement, we got this server under our management 3 weeks ago, and customer asked to upgrade urgently to 12. It's a governement agency, and the limit is due to certification matrix with application running against the database. We totaly agree with you about to switch to a new VM built from scratch, but probabiy this wont be possible, so we need to understand in deep what we could face in the migration step having this server and (we hope) a clone to test on. thanks again regards Marco Il 02.08.2023 16:57 Christoph Moench-Tegeder ha scritto: > ## marco.ptz@tiscali.it [1] (marco.ptz@tiscali.it [2]): > >> we have recently started to manage a production server running a 9.6 postgres. > > Which is EOL for nearly two years now: > https://www.postgresql.org/support/versioning/ [3] > >> We have to upgrade to postgres 12.x > > Which is going EOL in little over one year's time. > > You should look into https://yum.postgresql.org/packages/ [4]where you > can get packages with some real production life time. > ks in /usr/bin be created by alternatives once the 9.2 release w > d/deinstalled/deleted? > > The symlinks would be created by registering the repective versions > with the alternatives system - usually that happens in the post-install > scripts of the RPMs. You could do that manually (after removing 9.2) > or maybe by re-installing your current (ancient) packages. Cleanest > so> toph -- Spare Space. --=_9d5e954cf632b9ea0aebb6896bb0feec Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8
Hi Christoph,

thank you very much for your time.
We kn= ow the 2 releases are old, unfortunately we cannot change requirement,
we got this server under our management 3 weeks ago, and customer asked to= upgrade urgently to 12.
It's a governement agency, and the limit is = due to certification matrix with application running
against the data= base.

We totaly agree with you about to switch to a new VM built= from scratch, but probabiy this wont be possible,
so we need to under= stand in deep what we could face in the migration step having this server a= nd (we hope) a clone to test on.

thanks again
regards
Marco


Il 02.08.2023 16:57 Christoph Moench-Tegeder ha scritto:

## marco.ptz@tiscali.it (<=
a href=3D"mailto:marco.ptz@tiscali.it">marco.ptz@tiscali.it):
we have recently started to manage a = production server running a 9.6 postgres.
Which is EOL for nearly two years now:
https://www.post=
gresql.org/support/versioning/
We have to upgrade to postgres 12.x
Which is going EOL in little over one year's time.

You should look into https=
://yum.postgresql.org/packages/where you
can get packages with some real production life time.
At present in /usr/bin there are not = links as aspected for use with alternatives, but there are files belonging = to 9.2 version except for pg_basebackup:
That sounds severly broken, as if you installed CentOS original
"postgresql" package (CentOS 7 ships with the really ancient 9.2).
Check rpm and yum where that came from and then it's time for some
cleanup. In the mean time, make sure to always call all PostgreSQL
utilities with full path.
Could we have trouble having 9.6 and = 12 running in the same time (we will upgrade with pg_upgrade) in such serve= r?
For pg_upgrade, you will need both the old and new binaries installed=
=2E
HOW can we to fix the presence of rel= ease 9.2 files in /usr/bin?
Maybe best use the upgrade opportunity to move everything to a clean
installation on a new VM?
Will the simbolic links in /usr/bin b= e created by alternatives once the 9.2 release will be dropped/deinstalled/= deleted?
The symlinks would be created by registering the repective versions
with the alternatives system - usually that happens in the post-install
scripts of the RPMs. You could do that manually (after removing 9.2)
or maybe by re-installing your current (ancient) packages. Cleanest
solution would be a new server - who knows what other surprises are
hidden on that machine?

Regards,
Christoph

-- Spare Space. 

--=_9d5e954cf632b9ea0aebb6896bb0feec--