Not able to upgrade Postgres Flexible Server from 12 to higher versions

Rohit Gandhi M 0 Reputation points
2025-10-24T12:00:15.6433333+00:00

I have been trying to upgrade postgres version from 12 to higher version for a long period of time, and whenever tried it always gives me this error:-

The value of the 'Version' should be in: []. Verify that the specified parameter value is correct. (Code: ParameterOutOfRange)

Attaching the snapshot as well for the reference.

If someone could please help...

User's image

Azure Database for PostgreSQL
{count} votes

2 answers

Sort by: Most helpful
  1. Kalyani Kondavaradala 4,595 Reputation points Microsoft External Staff Moderator
    2025-10-27T13:39:31.7+00:00

    Hi Rohit Gandhi M,

    Thanks for approaching Microsoft Q&A!

    Before performing a major upgrade, Azure conducts pre-check operations. If these checks fail (for instance, due to unsupported configurations or extensions), the upgrade does not proceed. You might want to check if your server has any read replicas enabled, unsupported extensions, or specific configurations that could be blocking the upgrade.

    Please go through this document for limitations and the pre requisites

    https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-major-version-upgrade

    Could you please confirm the below detail.

    • Can you please tell which exact version you are trying to upgrade 13 or 14 or 15 or 16 or 17?
    • Please confirm which region you are current PostgreSQL server presents?

    whenever you deploy any server please check the service health of the resource and azure status in that region so that you will get to know whether there is any ongoing issues on that region.

    Limitations:

    In-place major version upgrades do not support all PostgreSQL extensions. The upgrade will fail during the precheck if unsupported extensions are found.

    • The following extensions are supported for regular use, but will block an in-place major version upgrade if present. Remove them before the upgrade and re-enable them after, if supported on the target version: timescaledb, dblink, orafce, postgres_fdw.
    • The following extensions are non-persistent utility extensions and will need to be dropped and re-created after the upgrade by design: pg_repack, hypopg.
    • When upgrading to PostgreSQL 17, the following extensions are not supported and must be removed before upgrade. You may re-enable them only if supported on the target version: age, azure_ai, hll, pg_diskann, pgrouting.

    Note: If any of these extensions appear in the azure.extensions server parameter, the upgrade will be blocked. Remove them from the parameter before starting the upgrade.

    Kindly consider upvoting if the provided information helpful, please let us know if you have further queries on this happy to help you.

    Thanks!

    Kalyani


  2. Carlos Jesús Rojas Gutiérrez 435 Reputation points
    2025-11-04T03:25:18.0866667+00:00

    El error “ParameterOutOfRange” al intentar actualizar PostgreSQL Flexible Server desde la versión 12 indica que no hay versiones superiores disponibles para actualización directa en esa instancia. Esto puede deberse a limitaciones del servicio o configuración regional.

    ¿Por qué ocurre este error?

    Azure PostgreSQL Flexible Server no permite actualizaciones in-place entre versiones mayores (por ejemplo, de 12 a 13 o 14).

    El campo 'Version' espera un valor válido, pero si el sistema devuelve [], significa que no hay versiones disponibles para esa operación.

    Esto puede deberse a:

    Restricciones en la región donde está desplegado el servidor.

      Limitaciones del tipo de SKU o configuración actual.
    
      
         La versión deseada no está habilitada para actualizaciones automáticas.
    ```###      Soluciones recomendadas
    
    #### 1. **Verifica versiones disponibles en tu región**
    
    Usa Azure CLI para listar versiones compatibles:
    
    bash
    
    
    ```dockerfile
    az postgres flexible-server list-skus --location <tu-región>
    

    Esto te mostrará las versiones que puedes usar en nuevas instancias.

    2. Crear una nueva instancia con versión superior

    Como no se puede actualizar directamente, la solución es:

    Crear una nueva instancia con PostgreSQL 13, 14 o 15.

    Migrar los datos desde la instancia actual (v12) usando herramientas como:

    pg_dump y pg_restore

      `Azure Database Migration Service`
    
      
         `Data-in replication` si aplica
    ```#### 3. **Revisar documentación oficial**
    
    Microsoft recomienda migrar manualmente entre versiones mayores:
    
    Guía oficial de migración de PostgreSQL Flexible Server
    
    ### 
    
    ###   `az postgres flexible-server list-skus --location <tu-región>
    `
    
    Esto te mostrará las versiones que puedes usar en nuevas instancias.
    
    #### 2. **Crear una nueva instancia con versión superior**
    
    Como no se puede actualizar directamente, la solución es:
    
    Crear una nueva instancia con PostgreSQL 13, 14 o 15.
    
    Migrar los datos desde la instancia actual (v12) usando herramientas como:
    
       `pg_dump` y `pg_restore`
       
    ```sql
      `Azure Database Migration Service`
    
      
         `Data-in replication` si aplica
    ```#### 3. **Revisar documentación oficial**
    
    Microsoft recomienda migrar manualmente entre versiones mayores:
    
    Guía oficial de migración de PostgreSQL Flexible Server
    
    ###
    
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.