| From: | Gabriel Guillem Barceló Soteras <gbarcelo(at)parlamentib(dot)es> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | PostgreSQL Repos and archiving |
| Date: | 2026-05-12 06:24:46 |
| Message-ID: | DU0PR08MB8637804BE1B83CB490DD2D78A6392@DU0PR08MB8637.eurprd08.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-05-12 07:41:21 | Re: PostgreSQL Repos and archiving |
| Previous Message | Gambhir Singh | 2026-05-11 12:31:05 | Alter the datatype on all tables present in the database (bigint to varchar) |