# Ensure the Postgres engine version is current / not end-of-life

- Source: https://support.icompaas.com/support/solutions/articles/a_1790103904554252-ensure-the-postgres-engine-version-is-current-not-end-of-life
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Supabase cloud](https://support.icompaas.com/support/solutions/c_1790103054038308) › [supabase checks](https://support.icompaas.com/support/solutions/folders/f_1790103067540538)
- Last updated: 2026-09-22
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure each project runs a supported Postgres version and is upgraded when Supabase releases a newer version. Projects should not stay on deprecated or end-of-life versions, which no longer receive security fixes and may be upgraded automatically by Supabase.

**Rationale**

Older Postgres versions stop receiving security patches and bug fixes over time. Running an outdated version leaves known vulnerabilities unpatched and blocks access to newer security features, such as Network Restrictions on some older versions. Upgrading on a planned schedule is safer than being forced to upgrade when a version is removed.

**Impact**

-   Receives the latest security fixes
    
-   Unlocks newer platform features
    
-   Upgrades cause downtime and may need extension changes
    

**Default Value**

Projects stay on the Postgres version they were created with until they are upgraded. Supabase notifies owners and may automatically upgrade projects on deprecated versions.

**Pre-Requisites**

-   Project Owner or Admin role
    
-   A planned maintenance window
    
-   A recent backup
    
-   Removal of any extensions not supported in the new version
    

**Test Plan**

1.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
2.  Select your project.
    
3.  Open Project Settings and select Infrastructure (in newer dashboards this is under General).
    
4.  Check the current Postgres version.
    
5.  If an upgrade is offered or the version is deprecated, follow the implementation steps.
    

**Implementation Steps**

1.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
2.  Select your project.
    
3.  Take a backup of the database.
    
4.  Open Project Settings and select Infrastructure (in newer dashboards this is under General).
    
5.  Review any warnings, such as unsupported extensions, and fix them.
    
6.  Select Upgrade project and confirm.
    
7.  After the upgrade, test the application.
    

**Backout Plan**

1.  An in-place upgrade cannot be reversed. If needed, restore the backup taken before the upgrade to a new project.
    
2.  If the upgrade itself fails, Supabase brings the original database back online automatically.
    

**Reference**

-   [https://supabase.com/docs/guides/platform/upgrading](https://supabase.com/docs/guides/platform/upgrading)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.