In PostGIS someone had issue upgrading pgrouting because they were using
pgrouting functions in views that had changed signatures.
This is going to be more of an issue in pgRouting 3.7 and 4.0 when we change
the signatures of a lot more functions.
Here is the postgis ticket: #5584 (PostGIS Upgrade Issue) – PostGIS
For now the workaround is to have the user first do:
DROP EXTENSION pgrouting; – which will fail
And then a catalog all the views it complains about and save the source code
of them
Then do:
DROP EXTENSION pgrouting CASCADE;
In PostGIS, Sandro came up with a neat way of renaming old functions and
notifying users they need to drop those after upgrade. This works because
views reference the OID of a function and not the function by name.
I have to double check, but I think he also has it rebuild the affected
views if he can.
Thanks,
Regina