Message-ID: <504d3ebc45b86cf8d7ff1f3772e20f86a09d85ce.camel@cybertec.at>
Subject: Re: PostgreSQL Repos and archiving
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Gabriel Guillem =?ISO-8859-1?Q?Barcel=F3?= Soteras
	 <gbarcelo@parlamentib.es>, Pgsql-admin <pgsql-admin@lists.postgresql.org>
Date: Tue, 12 May 2026 09:41:21 +0200
In-Reply-To: 
 <DU0PR08MB8637804BE1B83CB490DD2D78A6392@DU0PR08MB8637.eurprd08.prod.outlook.com>
References: 
	<DU0PR08MB8637804BE1B83CB490DD2D78A6392@DU0PR08MB8637.eurprd08.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/504d3ebc45b86cf8d7ff1f3772e20f86a09d85ce.camel%40cybertec.at>
Precedence: bulk

On Tue, 2026-05-12 at 06:24 +0000, Gabriel Guillem Barcel=C3=B3 Soteras wro=
te:
> I=E2=80=99m looking for guidance on how others are handling PGDG YUM repo=
sitory maintenance on RHEL-like systems.
>=20
> In our environment, we installed PostgreSQL 15 client libraries (postgres=
ql15,libpq, etc.) across several
> hosts at a time when PostgreSQL 13 was still supported. As a result, thep=
gdg-redhat-all.repo=C2=A0file enabled
> multiple repositories (includingpgdg13).
>=20
> Now that PostgreSQL 13 has reached end-of-life, its repository has been m=
oved to the archive, and the
> original URL no longer works. Because the repository remains enabled, dnf=
 update=C2=A0fails when refreshing
> metadata. DNF skip_if_unavailabledoes not work because of the error code =
returned by the old repo (410?)
>=20
> How are handling this situation apart from deleting old repo?

The proper way of dealing with that is to keep the package pgdg-redhat-repo=
 updated.
Then the reference to the repositories of versions that are no longer suppo=
rted will
vanish automatically, and you won't encounter the problem.

At the same time, keep updating your installations to the latest minor rele=
ase.
That way, you can be certain to have the latest minor release for v13 when =
it goes
out of support.

Needless to say, you should upgrade way before a version goes out of suppor=
t.

Yours,
Laurenz Albe