public inbox for [email protected]  

help / color / mirror / Atom feed

From: =?Windows-1252?Q?Gabriel_Guillem_Barcel=F3_Soteras?= <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: PostgreSQL Repos and archiving
Date: Tue, 12 May 2026 06:24:46 +0000
Message-ID: <DU0PR08MB8637804BE1B83CB490DD2D78A6392@DU0PR08MB8637.eurprd08.prod.outlook.com> (raw)

Hello,

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, the pgdg-redhat-all.repo file enabled multiple repositories (including pgdg13).

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?


Gabriel B.

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: PostgreSQL Repos and archiving
  In-Reply-To: <DU0PR08MB8637804BE1B83CB490DD2D78A6392@DU0PR08MB8637.eurprd08.prod.outlook.com>

* 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