Attempt to upgrade Azure Database for PostgreSQL fails pre-check

Question

Trying to upgrade our PostgreSQL server's major version number using the "upgrade" button from within the Portal view of this resource, but it fails the precheck. Copied the error message below. We'd like to upgrade to version 17. Thank you.

{

"message": "The major version upgrade failed precheck."

}

Answer 1

Hi Andrew Reid

We reviewed the backend logs for the major version upgrade from PostgreSQL version 14 to version 17 and observed that the operation was blocked during the pre-check phase. The failure is related to the extension pg_failover_slots, which is currently configured under shared_preload_libraries. At present, upgrading this library from version 14 to 17 is not supported, which is preventing the major version upgrade from proceeding.  

To move forward, the pg_failover_slots entry will need to be removed from shared_preload_libraries before reinitiating the upgrade. You have removed the pg_failover_slots from shared_preload_libraries, and now the server has successfully upgraded to version 17.

Answer 2

The error message indicating that the major version upgrade failed precheck suggests that there are compatibility issues or unsupported configurations in your current setup. Here are some common reasons why the precheck might fail when attempting to upgrade to version 17:

1. Unsupported Server Configurations: Ensure that there are no read replicas present, as they must be deleted before the upgrade. Additionally, check your network traffic rules to ensure that they allow traffic on the necessary ports (5432 and 6432).
2. Logical Replication Slots: If you are using logical replication slots, they are not supported during the upgrade process.
3. Storage Type: Ensure that your server is not using SSDv2 storage, as it is not eligible for major version upgrades.
4. Extensions: Certain PostgreSQL extensions may block the upgrade. You need to remove unsupported extensions before proceeding with the upgrade.
5. Configuration Issues: Check if your server's configurations, such as authentication methods or event triggers, are compatible with version 17.

To resolve the issue, review the detailed error message from the precheck logs, which should provide more specific information about what is causing the failure. Address the identified issues and try the upgrade again.