PostgreSQL retires its RPM repositories for RHEL 10.0 and 9.6

PostgreSQL retires its RPM repositories for RHEL 10.0 and 9.6

20 October 2026: The PostgreSQL project's RPM repository team is retiring the repositories it builds for Red Hat Enterprise Linux 10.0 and 9.6 and moving them to its YUM archive, where they "will not receive further updates". The same applies to Rocky Linux and AlmaLinux 10.0 and 9.6.

Not yet independently verified. The project's post gives no exact date for the switch, saying only that the repositories "are being retired". We will update this when it can be confirmed, and remove this note.

What changes

All PostgreSQL major versions built for those two minor releases, including PostgreSQL 18, stay available in the archive, so existing servers can still install packages. What stops is new builds: future PostgreSQL minor releases, including security fixes, will not be published for these targets. The rolling EL-10 and EL-9 repository RPMs, which follow the current minor release of each major version, are not affected.

Servers pinned to a minor release

The change hits servers that are pinned to a specific minor release of RHEL or a compatible distribution, rather than tracking the latest one. That is common where a hardware certification, a vendor support matrix or a regulated change process fixes the operating system version, and it is also typical of Extended Update Support set-ups. On such servers, PostgreSQL packages from the PGDG repository will quietly stop getting updates, and a later PostgreSQL security release will not arrive through the normal channel. Nothing breaks on the day the repository moves, which is what makes the change easy to miss: the server keeps running the build it already has, and the next dnf update simply finds nothing new for PostgreSQL.

Moving on, or living with the archive

The project gives two options: update to a newer minor release of the operating system, or point the server at the archive, accepting that it will not receive further updates. The archived-repositories section of its repository packages page generates the repository file and install commands for each distribution version, architecture and PostgreSQL version.

For most teams the first option is the right one, because staying on a frozen repository means missing PostgreSQL's own security fixes. Database and platform teams should check which minor release each database host runs and which repository file it uses, and plan the operating system update alongside the next PostgreSQL minor upgrade. Questions can go to the project's packaging mailing list or its issue tracker. Our RDBMS software category lists 35 products.

Related on TrustList:

• DigitalOcean caps PostgreSQL and MySQL Standard Edition at 4 GiB RAM and drops standby nodes: 15 October for new accounts, 30 November 2026 for all
• PgBouncer 1.26.1 fixes a SCRAM login bypass and two hang bugs
• PostgreSQL 19 now due on 19 November after late feature reverts

Sources

• PostgreSQL: RHEL 10.0 and 9.6 repositories are being retired, 20 October 2026
• PostgreSQL YUM repository: archived repositories (read 2026-10-20), 20 October 2026