The PostgreSQL project has begun retiring the RHEL 10.0 and RHEL 9.6 repositories from the main PostgreSQL RPM repository. According to the announcement, both minor-release repositories have been moved to the PostgreSQL YUM archive, where all PostgreSQL major versions built for them remain available, including PostgreSQL 18. Users still running these specific minor releases — or the equivalent Rocky Linux / AlmaLinux 10.0 or 9.6 builds — must now either upgrade to a newer minor release or switch their package configuration to the archived repositories.
- The RHEL 10.0 and RHEL 9.6 repositories are removed from the main PostgreSQL RPM repository.
- All PostgreSQL major versions built for those minor releases, including PostgreSQL 18, are available in the PostgreSQL YUM archive.
- The rolling
EL-10andEL-9repository RPMs are not affected and continue to receive updates. - Archived repositories will not receive further updates.
- The repository packages page now includes an archived repositories section that generates the repository file and install commands for each distribution version, architecture, and PostgreSQL version.
- Questions can be directed to
[email protected]or the project issue tracker.
For developers, the key point is that minor-release pins are no longer maintained. If a system is still pinned to RHEL 10.0 or 9.6, package installs and updates may fail once the old repository paths stop resolving. The recommended path is to update the host to a newer minor release and keep using the rolling EL-10 or EL-9 repository, which remains supported. Teams that cannot upgrade immediately can reconfigure dnf or yum to point at the archived repository generated by the repository packages page, but they should treat that setup as frozen: it will not receive security or bug-fix updates. Planning the move now avoids surprises during routine patching or CI image rebuilds that rely on the PostgreSQL RPM repository.
Source: https://www.postgresql.org/about/news/rhel-100-and-96-repositories-are-being-retired-3411/