# PostgreSQL retires RHEL 9.6 and 10.0 RPM repositories, ending package updates on those minor releases The PostgreSQL RPM maintainers moved RHEL 9.6 and 10.0 package repositories into an archive on October 20. Rocky Linux and AlmaLinux installations on those minor releases face the same change: archived packages remain available, but no further updates will arrive there. PGDG's 20 October repository retirement requires RHEL, Rocky and AlmaLinux 9.6/10.0 operators to update their OS minor release or deliberately switch to the frozen archive. Rolling EL9 and EL10 repository packages are unaffected. - Status: Active - Published: 2026-10-21T19:17:15+13:00 - Updated: 2026-10-21T19:17:15+13:00 - Categories: Cloud & Infrastructure, Deployment & DevOps, Databases & Storage - Tags: Linux, PostgreSQL, security - Canonical HTML: https://beyondthe.news/dossiers/postgresql-pgdg-rhel-9-6-10-0-rpm-repos-archived-no-updates ## 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. ## Key details - PGDG announcement posted October 20, 2026. - Affected: RHEL/Rocky/AlmaLinux 9.6 and 10.0 dedicated PGDG RPM repositories. - Archived packages, including PostgreSQL 18 builds, remain available. - Archived repositories receive no further updates. - Rolling EL9 and EL10 repository RPMs are not affected. - Recommended paths: upgrade OS minor release or intentionally use archive. ## Builder takeaways - Inventory RHEL/Rocky/AlmaLinux 9.6 and 10.0 hosts using PGDG RPM packages. - Do not confuse access to archived RPMs with ongoing security maintenance. - Prefer a tested supported minor-release upgrade over silently pinning to a frozen repository. - Verify PostgreSQL extensions, OpenSSL compatibility and backup restore procedures after repository changes. ## What to watch - Any further PGDG retirement notices for adjacent OS minor releases. - Updated packaging support matrix and repository generator behaviour. - Operator reports of package dependency failures or unintended archive pinning. ## Uncertainties - No fleet-wide count of affected hosts was published. - The advisory does not guarantee compatibility of old PostgreSQL extension builds with newer OS minor releases. - No independent end-to-end migration was performed. ## Sources - [RHEL 10.0 and 9.6 repositories are being retired](https://www.postgresql.org/about/news/rhel-100-and-96-repositories-are-being-retired-3411/) — PostgreSQL PGDG RPM Repository · primary package-maintainer advisory · 2026-10-20T00:00:00+13:00. Affected OS minor versions, archive location, rolling-repo exception and no further updates. - [PostgreSQL RPM repository now supports multiple RHEL minor versions](https://www.postgresql.org/about/news/postgresql-rpm-repository-now-supports-multiple-rhel-minor-versions-3202/) — PostgreSQL PGDG RPM Repository · primary packaging background · 2025-12-27T00:00:00+13:00. OpenSSL dependency incompatibility that prompted minor-specific builds. - [Archived PostgreSQL YUM repositories](https://yum.postgresql.org/repopackages/#archivedrepos) — PostgreSQL PGDG · primary repository configuration. Official archive generator for distribution version, architecture and PostgreSQL version.