This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 97%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELG%3C/text%3E%3C/svg%3E)
Based on this documentation https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-supported-versions#postgresql-version-16 Postgres 16 is generally available.
I have this instance https://portal.azure.com/#@softpoint.sk/resource/subscriptions/744ab270-69d6-4658-a16e-c390e2d9c4c6/resourceGroups/qFlowSaaSTestWEU-rg/providers/Microsoft.DBforPostgreSQL/flexibleServers/weu-flowis-prod-postgres-sequor/overview however I don't see option to promote it to Postgres 16, even if I stop the instance.
It still says "You are already running the latest major PostgreSQL version available." but that's not true since I'm running 15 and 16 is available. How can I upgrade it please?
@Ladislav Gallay Thank you for reaching out.
My understanding is that you are not able to perform a version upgrade to 16 for your Azure PostgreSQL flexible server.
Could you please to do this using CLI Major Version Upgrade of a flexible server - Flexible Server with Azure CLI
Limitations
If in-place major version upgrade pre-check operations fail, then the upgrade aborts with a detailed error message for all the below limitations.
In-place major version upgrade currently doesn't support read replicas, so if you have a read replica enabled server, you need to delete the replica before performing the upgrade on the primary server. After the upgrade, you can recreate the replica.
In-place major version upgrade doesn't support certain extensions and there are some limitations to upgrading certain extensions. The extensions Timescaledb, pgaudit, dblink, orafce, pg_partman, and postgres_fdw are unsupported for all PostgreSQL versions.
When upgrading servers with PostGIS extension installed, set the search_path server parameter to explicitly include the schemas of the PostGIS extension, extensions that depend on PostGIS, and extensions that serve as dependencies for the below extensions. e.g postgis,postgis_raster,postgis_sfcgal,postgis_tiger_geocoder,postgis_topology,address_standardizer,address_standardizer_data_us,fuzzystrmatch (required for postgis_tiger_geocoder).
Regards,
Oury
Thank you. I tried also CLI but it ends up with the similar error.
az postgres flexible-server upgrade: '16' is not a valid value for '--version'. Allowed values: 12, 13, 14, 15.
It says "version 16" is not a valid value. Why?
Is it possible that despite Postgres 16 being available, the upgrade via Azure is not possible and the only way is to create a new DB and copy (pg_dump+psql) data manually?
I tried this even on a newly created empty Postgres 15 server, which I just created, so there are no extensions, replicas, or anything. It is a simple new Postgres 15 flexible server, and upgrading to Postgres 16 was still not possible.
I believe upgrade to version 16 for an existing Azure PostgreSQL flex is not yet available using portal functionality or CLI.
But when creating a new Server, you will see the option on selecting version 16. Let me get further clarification on this internally with the team and get back.
Regards,
Oury
@Ladislav Gallay I was able to confirm this internally.
The “In-Place Major Version Upgrade” (MVU) functionality for PG16 is not yet available, and this is being currently worked.
You can however still create a new Flex PG instance on Postgres 16 (hence the doc says it is supported).
Regards,
Oury
When is the upgrade from PG 15 to 16 going to be available, please?
It is currently in their backlog, but we don't have an exact ETA for now. But I will check and update the thread so that other community members have that information too.
Regards,
Oury
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 57.00000000000001%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Hello @Oury Ba-MSFT I will Appreciate If you would add That information ( That We could not upgrade to PostgreSQL 16 only to create a new one) To Azure Documentation. Currently You can't find out about the issue until you come across it