- Newest
- Most votes
- Most comments
This seems resolved now,
not sure if ti was just a temporary issue that got resolved after a new attempt, like in https://repost.aws/questions/QUdN7XUmg8R9u-qtZNy_T-_w/access-log-file-from-failed-upgrade-from-postgresql-10-7-to-11-2#ANjDKCqn5qRqCssfxMEqzJaQ
or if it was still an issue related to postgis_raster extension. In fact after updating the postgis extension, the postgis_raster was still trying to use some old 2.* system libraries, and I followed steps reported in https://repost.aws/questions/QUP1Suk7DnSMqEZMCBkOGoBQ/rds-postgresql-engine-upgrade-from-10-21-to-14-4-version#ANpno0pqFPQXO9HtAgs4Tmqw
but maybe that was not enough, so I also tried https://postgis.net/stuff/uninstall_rtpostgis.sql before triggering again the cluster upgrade, that this time worked without errors.
We'll check how it goes, doing the same process in the other environments.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
This worked also with another cluster in another environment/account