When i upgrade my azure postgres flexi server version from 11 to 16 it is giving error as "internal server error".

Question

When i upgrade my azure postgres flexi server version from 11 to 16 it is giving error as "internal server error".

Suraj Jaiswal 0

Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-13T08:48:09.95+00:00
Hi Suraj Jaiswal

Greetings!

As we understand that, you are running into an "internal server error" while trying to upgrade your Azure PostgreSQL flexible server from version 11 to 16.

Here are a few things you might want to check:

Pre-Upgrade Checks: Azure performs a precheck before allowing a major version upgrade. If there are any incompatible settings or unsupported extensions, it will block the upgrade and provide an error message. Make sure to check the logs for any details regarding what might have caused the precheck to fail.

Unsupported Configurations: Ensure that you don’t have any read replicas. You will need to delete those before proceeding with the upgrade. Check your network settings. Network traffic rules could block the upgrade, so confirm that your server can send/receive traffic on necessary ports (5432 and 6432). If you are using SSDv2 storage, note that it is not eligible for major version upgrades.

Extension Compatibility: Make sure that any extensions you are using are compatible with PostgreSQL 16. Some extensions like timescaledb, pg_partman, and others are not supported across major version transitions, which could lead to failure.

Backup: Always ensure you have a reliable backup before attempting a major upgrade. This allows you to restore to the previous state if anything goes wrong.

Downtime: Keep in mind that although the process typically requires a short downtime, long-running transactions can extend this.

I would request you to refer the below mentioned link for an additional information.

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

https://learn.microsoft.com/en-us/answers/questions/2245270/error-upgrading-postgresql-flexible-server

I hope this information helps. Please do let us know if you have any further queries.
Suraj Jaiswal 0 Reputation points

2025-06-13T09:16:08.6866667+00:00

Hi Vijayalaxmi Kattimani,

SELECT * FROM pg_extension;
extname | extowner | extnamespace | extrelocatable | extversion | extconfig | extcondition -----------+----------+--------------+----------------+------------+---------------------------+--------------- plpgsql | 10 | 11 | f | 1.0 | | pg_cron | 10 | 2200 | f | 1.4-1 | {24738,24736,24759,24757} | {"","","",""} azure | 10 | 11 | t | 1.1 | | pgaadauth | 10 | 11 | t | 1.4 | | (4 rows)

above are the extensions available on my server

I have allowed some limit public ip address in my server's network setting.

There is no replications setup on my server.

My server's storage type is Premium SSD.

Kindly let me know what's the issue or what else need to check ?
Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-13T11:28:32.9433333+00:00

Hi Suraj Jaiswal

Thank you for the details.

Based on the extensions you listed (pg_cron, azure, and pgaadauth), we can confirm that they are compatible with PostgreSQL 16. You also confirmed that there are no read replicas connected to your server during the upgrade, which is ideal.

Regarding your network settings, you mentioned that public access is restricted to a limited set of IP addresses. Please note that such restrictions can impact the upgrade process. During a major version upgrade, Azure may internally create and manage temporary resources (e.g., containers, virtual machines, or replicas), which require connectivity.

If your server only allows a limited IP range and Azure’s internal service IPs are not included, the upgrade may fail due to network restrictions. We recommend verifying that your firewall or network settings allow traffic on ports 5432 and 6432, as any Network Security Groups (NSGs) or firewall rules blocking these ports can impede the upgrade.

To ensure a successful upgrade, we advise temporarily allowing all IP addresses (0.0.0.0/0), or at least ensuring that Azure service IP ranges are permitted. Once the upgrade is complete, you can revert to your original restricted IP list.

If possible, consider using Private Access with Private DNS Zone integration, as this minimizes such issues by keeping all communication within the Azure Virtual Network.

If the issue still persists, could you please share the requested details via private message as it will help us conduct a more thorough investigation.

I hope, This response will address your query and helped you to overcome on your challenges. Please do let us know if you have any further queries.
Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-17T01:16:00.45+00:00

Hi Suraj Jaiswal
We are reaching out to the internal team to get more information related to your query and will get back to you as soon as we have an update.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-25T09:17:58.0533333+00:00

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Oury Ba-MSFT 20,911 Reputation points Microsoft Employee Moderator

2025-06-26T14:58:33.44+00:00

@Suraj Jaiswal Checking if you had the chance to run the below script.

Please let me know if you need help to do the above.

Regards,

Oury

1 answer

Your answer

Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-13T08:48:09.95+00:00

Hi Suraj Jaiswal

Greetings!

As we understand that, you are running into an "internal server error" while trying to upgrade your Azure PostgreSQL flexible server from version 11 to 16.

Here are a few things you might want to check:

Pre-Upgrade Checks: Azure performs a precheck before allowing a major version upgrade. If there are any incompatible settings or unsupported extensions, it will block the upgrade and provide an error message. Make sure to check the logs for any details regarding what might have caused the precheck to fail.

Unsupported Configurations: Ensure that you don’t have any read replicas. You will need to delete those before proceeding with the upgrade. Check your network settings. Network traffic rules could block the upgrade, so confirm that your server can send/receive traffic on necessary ports (5432 and 6432). If you are using SSDv2 storage, note that it is not eligible for major version upgrades.

Extension Compatibility: Make sure that any extensions you are using are compatible with PostgreSQL 16. Some extensions like timescaledb, pg_partman, and others are not supported across major version transitions, which could lead to failure.

Backup: Always ensure you have a reliable backup before attempting a major upgrade. This allows you to restore to the previous state if anything goes wrong.

Downtime: Keep in mind that although the process typically requires a short downtime, long-running transactions can extend this.

I would request you to refer the below mentioned link for an additional information.

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

https://learn.microsoft.com/en-us/answers/questions/2245270/error-upgrading-postgresql-flexible-server

I hope this information helps. Please do let us know if you have any further queries.
Suraj Jaiswal 0 Reputation points

2025-06-13T09:16:08.6866667+00:00

Hi Vijayalaxmi Kattimani,

SELECT * FROM pg_extension;
extname | extowner | extnamespace | extrelocatable | extversion | extconfig | extcondition -----------+----------+--------------+----------------+------------+---------------------------+--------------- plpgsql | 10 | 11 | f | 1.0 | | pg_cron | 10 | 2200 | f | 1.4-1 | {24738,24736,24759,24757} | {"","","",""} azure | 10 | 11 | t | 1.1 | | pgaadauth | 10 | 11 | t | 1.4 | | (4 rows)

above are the extensions available on my server

I have allowed some limit public ip address in my server's network setting.

There is no replications setup on my server.

My server's storage type is Premium SSD.

Kindly let me know what's the issue or what else need to check ?
Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-13T11:28:32.9433333+00:00

Hi Suraj Jaiswal

Thank you for the details.

Based on the extensions you listed (pg_cron, azure, and pgaadauth), we can confirm that they are compatible with PostgreSQL 16. You also confirmed that there are no read replicas connected to your server during the upgrade, which is ideal.

Regarding your network settings, you mentioned that public access is restricted to a limited set of IP addresses. Please note that such restrictions can impact the upgrade process. During a major version upgrade, Azure may internally create and manage temporary resources (e.g., containers, virtual machines, or replicas), which require connectivity.

If your server only allows a limited IP range and Azure’s internal service IPs are not included, the upgrade may fail due to network restrictions. We recommend verifying that your firewall or network settings allow traffic on ports 5432 and 6432, as any Network Security Groups (NSGs) or firewall rules blocking these ports can impede the upgrade.

To ensure a successful upgrade, we advise temporarily allowing all IP addresses (0.0.0.0/0), or at least ensuring that Azure service IP ranges are permitted. Once the upgrade is complete, you can revert to your original restricted IP list.

If possible, consider using Private Access with Private DNS Zone integration, as this minimizes such issues by keeping all communication within the Azure Virtual Network.

If the issue still persists, could you please share the requested details via private message as it will help us conduct a more thorough investigation.

I hope, This response will address your query and helped you to overcome on your challenges. Please do let us know if you have any further queries.
Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-17T01:16:00.45+00:00

Hi Suraj Jaiswal
We are reaching out to the internal team to get more information related to your query and will get back to you as soon as we have an update.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-25T09:17:58.0533333+00:00

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Oury Ba-MSFT 20,911 Reputation points Microsoft Employee Moderator

2025-06-26T14:58:33.44+00:00

@Suraj Jaiswal Checking if you had the chance to run the below script.

Please let me know if you need help to do the above.

Regards,

Oury

Answer 1

@Suraj Jaiswal Thank you for reaching out and sorry about the issue you are facing.

Could you please run the below script.

Root cause: sql_identifier is a domain used in system catalogs and information schema. It is not meant for use in user tables, because its definition can change between versions

Next steps:

Use this query in each database to identify where sql_identifier is used SELECT n.nspname AS schema_name, c.relname AS table_name, a.attname AS column_name, t.typname AS data_typeFROM pg_attribute aJOIN pg_class c ON a.attrelid = c.oidJOIN pg_namespace n ON c.relnamespace = n.oidJOIN pg_type t ON a.atttypid = t.oidWHERE a.attnum > 0 AND NOT a.attisdropped AND t.typname = 'sql_identifier' AND n.nspname NOT IN ('pg_catalog', 'information_schema'); 2. Alter these columns to use any other compatible data_types
Alter these columns to use any other compatible data_types
Try the upgrade again

Please let me know the result.

Regards,

Oury

Share via

When i upgrade my azure postgres flexi server version from 11 to 16 it is giving error as "internal server error".

1 answer

Your answer