public inbox for pgsql-admin@postgresql.org  

help / color / mirror / Atom feed

From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Gabriel Guillem Barceló Soteras <gbarcelo@parlamentib.es>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: PostgreSQL Repos and archiving
Date: Tue, 12 May 2026 09:41:21 +0200
Message-ID: <504d3ebc45b86cf8d7ff1f3772e20f86a09d85ce.camel@cybertec.at> (raw)
In-Reply-To: <DU0PR08MB8637804BE1B83CB490DD2D78A6392@DU0PR08MB8637.eurprd08.prod.outlook.com>
References: <DU0PR08MB8637804BE1B83CB490DD2D78A6392@DU0PR08MB8637.eurprd08.prod.outlook.com>

On Tue, 2026-05-12 at 06:24 +0000, Gabriel Guillem Barceló Soteras wrote:
> I’m looking for guidance on how others are handling PGDG YUM repository maintenance on RHEL-like systems.
> 
> In our environment, we installed PostgreSQL 15 client libraries (postgresql15,libpq, etc.) across several
> hosts at a time when PostgreSQL 13 was still supported. As a result, thepgdg-redhat-all.repo file enabled
> multiple repositories (includingpgdg13).
> 
> Now that PostgreSQL 13 has reached end-of-life, its repository has been moved to the archive, and the
> original URL no longer works. Because the repository remains enabled, dnf update fails when refreshing
> metadata. DNF skip_if_unavailabledoes not work because of the error code returned by the old repo (410?)
> 
> 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 supported will
vanish automatically, and you won't encounter the problem.

At the same time, keep updating your installations to the latest minor release.
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 support.

Yours,
Laurenz Albe

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: laurenz.albe@cybertec.at, gbarcelo@parlamentib.es, pgsql-admin@lists.postgresql.org
  Subject: Re: PostgreSQL Repos and archiving
  In-Reply-To: <504d3ebc45b86cf8d7ff1f3772e20f86a09d85ce.camel@cybertec.at>

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

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