[postgis-users] Upgrade 12->13 stuck due to postgis / raster issue

[Roxanne Reid-Bennett]

Jim,

 

I did a search on this phrase:
 

 raster procs from "2.5.2 r17328" need upgrade 

I found a post from Regina from 2020 moving from 2.5.2 to 3. It might illumine a bit.

 

https://lists.osgeo.org/pipermail/postgis-users/2020-May/044225.html

 
 

And this one for someone who had 100% control of their PG hardware from last fall.
 

 

https://groups.google.com/g/postgis-users/c/26iNuhXFHgg

 


 

 

And this one from the AWS forums 
 

 

https://repost.aws/questions/QUEk9HG5x3Qq6sEB3lVmynUw/upgrade-from-postgres-12-7-r-1-to-13-3-r-1-stuck

 

which references this:

 

https://stackoverflow.com/questions/42634626/postgresql-upgrade-on-amazon-rds-blocked-by-postgis-version

 

which uses 
 

 

ALTER EXTENSION postgis UPDATE;


 

The observation in the last post about waiting overnight and things "magically being fixed", I saw during our dry run, not the production run, but definitely during the dry run.  Their observation about rebooting the PG server between upgrades isn't totally "off" either.
 

 

Posting in the AWS Forums might get some help from inside Amazon.

 

Or, if you have any level of support from AWS that would allow you get someone to "poke/prod" on disk, you might get a fix.  

 

Migrating the data is "of course" a last resort, but at least possible. 
 

 

Given my lack of knowledge of the upgrade steps, I've done what I can.  Good luck.
 

 

Roxanne
 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20230124/ef04a1f5/attachment.htm>