An Azure managed PostgreSQL database service for app development and deployment.
Hi @Todd Player
Thankyou for reaching microsoft Q&A!
The error indicates that the major version upgrade precheck is evaluating the effective search_path for the postgis_topology extension and is finding that the topology schema is not included.
For Azure Database for PostgreSQL Flexible Server, Microsoft requires the server-level search_path to explicitly include the schemas used by PostGIS and its dependent extensions before performing an in-place major version upgrade.
Although your current session returns:
"$user", public, topology
the upgrade precheck reports:
"$user", public
This suggests that the value being evaluated by the upgrade service may differ from the session-level value you are checking, potentially due to a role-level or server-level configuration.
As a next step, please verify the effective configuration at both the server and role levels, for example:
SHOW search_path;
SELECT rolname, rolconfig
FROM pg_roles
WHERE rolname IN ('azuresu', current_user);
Also verify where the extension is installed:
SELECT extname, n.nspname AS schema_name
FROM pg_extension e
JOIN pg_namespace n ON e.extnamespace = n.oid
WHERE extname = 'postgis_topology';
If postgis_topology is confirmed to be in the topology schema, the server search_path should include topology (and the other applicable PostGIS extension schemas) before retrying the upgrade.
Because azuresu is an Azure-managed role and cannot be modified by the customer administrator, if the upgrade precheck continues to report the same mismatch after the customer has configured the server-level search_path, this would require investigation by Microsoft Support/engineering to determine why the upgrade precheck is resolving a different effective search_path.
Please provide the output of the above queries, along with the PostgreSQL source and target major versions, so we can further assess the upgrade precheck failure.