Opened 13 months ago
Closed 2 months ago
#5550 closed defect (fixed)
Repackaging raster in a sandboxed system fails
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.5.0 |
Component: | upgrade/soft | Version: | 3.0.x |
Keywords: | pgextwlist | Cc: | wodan |
Description
It looks like re-packaging raster after upgrade from 2.x is not possible in a sandboxed system.
Change History (4)
comment:1 by , 12 months ago
comment:2 by , 11 months ago
Cc: | added |
---|---|
Component: | postgis → upgrade/soft |
Milestone: | PostGIS Fund Me → PostGIS 3.5.0 |
Owner: | changed from | to
As of commit [5c37f97329db3fc67b542d12ac31d73ad2f71c5a/git] we have CI under pgextwlist and it shows no problems with upgrade from 2.5 thanks to the included [e2bf40c322c8805ca13e5a270b98b2793ee436a3/git] commit changing ownership of functions during upgrade.
I would ask Dan Worthman to confirm this problem is now fixed
Original problem was:
postgres=> SELECT postgis_extensions_upgrade(); NOTICE: Updating extension postgis from 3.2.3 to 3.3.2 NOTICE: Packaging extension postgis_raster ERROR: Trying to add VIEW raster_columns to postgis_raster, got must be owner of extension postgis_raster (42501)
comment:3 by , 2 months ago
According to comment:2 we have no confirmation of this problem in the master branch so I'd close this ticket once a NEWS item about it is added
CI coverage of sandboxed systems ticket filed: #5566