What changed
On October 20, 2026, the PostgreSQL PGDG RPM Repository maintainers announced that the dedicated repositories for RHEL 10.0 and RHEL 9.6 had moved from the active RPM infrastructure to the PostgreSQL YUM archive. The change also affects corresponding Rocky Linux and AlmaLinux minor releases. The archive preserves packages built for those versions, including PostgreSQL 18, but maintainers explicitly state that archived repositories will not receive further updates. The rolling EL-10 and EL-9 repository RPMs are unaffected.
Why it matters
Teams pinning enterprise-Linux minor versions may stop receiving PostgreSQL package updates without a PostgreSQL server major-version change. Simply finding old packages in the archive is not the same as continuing to receive security fixes. Operators must decide between an OS minor upgrade and an explicit, risk-accepted frozen package source; this is particularly important for self-hosted SaaS and production database servers that automate yum/dnf patching.
Which systems are affected
The retirement is specific to PGDG RPM builds for RHEL 9.6 and 10.0 and matching Rocky Linux/AlmaLinux minor releases. It does not retire PostgreSQL 9.6 as a database version, nor all RHEL 9 or RHEL 10 repositories. The maintainers state that rolling EL-9 and EL-10 repository RPMs continue unaffected.
Why the repository matrix became more complicated
In December 2025 PGDG began building for multiple RHEL minor releases after an OpenSSL change between RHEL 9.6/9.7 and 10.0/10.1 produced dependency-resolution failures. That compatibility history helps explain why operators on older minor releases cannot assume newer RPMs will install cleanly. It does not establish that every host has already experienced a broken install.
Migration choices and risks
PGDG recommends upgrading to a newer OS minor release or selecting the relevant distribution, architecture and PostgreSQL version from the archived-repositories generator. An archived repo can preserve an old environment temporarily, but its frozen packages cannot deliver future security fixes. Before changing repository configuration, back up the system and verify the enabled RPM repository, package provenance, OpenSSL dependencies and available updates with the host's package manager.
Operational implications
Package-update monitoring that only checks whether dnf succeeds can miss the difference between a maintained source and a static archive. Operators should explicitly audit base OS minor version and PGDG repo URLs across their fleets, then test the OS minor upgrade with their PostgreSQL extensions and backup tooling. No new PostgreSQL server major version is required solely because the repository URL changed.