This looks like an issue specific to PostGIS on Amazon. The only work arounds I can think of such as first upgrading the PostGIS raster with the script approach would not work on Amazon because of the security restrictions they have put in place.
I think this is something they need to fix on their end. Thanks, Regina From: postgis-users [mailto:postgis-users-boun...@lists.osgeo.org] On Behalf Of Jin Igarashi Sent: Friday, May 29, 2020 12:01 AM To: postgis-users@lists.osgeo.org Subject: [postgis-users] Failed to upgrade PostGIS Raster from 2.2.5 to 3.0 on RDS Hi, We are currently using PostgreSQL 9.6.11 / PostGIS 2.3.7 on RDS. Because AWS started to support pg12/PostGIS3.0 recently, we are trying to upgrade our PostGIS database to 3.0. Then, I am facing a problem that could not upgrade postgis_raster to 3.0.0. I need some help if possible. My upgrading procedures are as follows. 1. I upgrade postgis from 2.2.5 to 2.3.7 on the current RDS database by following SQL. ALTER EXTENSION postgis UPDATE; 2. I upgrade PostgreSQL from 9.6.11 to 9.6.17 by AWS management console 3. Then, I upgrade PostGIS from 2.3.7 to 2.5.2 by using following SQL. ALTER EXTENSION postgis UPDATE TO '2.5.2'; WARNING: 'postgis.gdal_datapath' is already set and cannot be changed until you reconnect WARNING: 'postgis.gdal_enabled_drivers' is already set and cannot be changed until you reconnect WARNING: 'postgis.enable_outdb_rasters' is already set and cannot be changed until you reconnect There are some warnings appeared, but I think it's not problems...I continued. 4. I upgraded PostgreSQL from 9.6.17 to 12.2 by AWS management console 5. I upgraded PostGIS from 2.5.2 to 3.0.0 by following SQL. ALTER EXTENSION postgis UPDATE TO '3.0.0'; WARNING: unpackaging raster WARNING: PostGIS Raster functionality has been unpackaged HINT: type `SELECT postgis_extensions_upgrade(); to finish the upgrade. After upgrading, if you want to drop raster, run: DROP EXTENSION postgis_raster; ALTER EXTENSION Then, I tried as follow; SELECT postgis_extensions_upgrade(); NOTICE: Packaging extension postgis_raster WARNING: 'postgis.gdal_datapath' is already set and cannot be changed until you reconnect WARNING: 'postgis.gdal_enabled_drivers' is already set and cannot be changed until you reconnect WARNING: 'postgis.enable_outdb_rasters' is already set and cannot be changed until you reconnect ERROR: cannot create temporary table within security-restricted operation CONTEXT: SQL statement "CREATE EXTENSION postgis_raster FROM unpackaged" PL/pgSQL function postgis_extensions_upgrade() line 48 at EXECUTE After running "SELECT postgis_extensions_upgrade();", its error appeared and I could not upgrade postgis_raster from 2.5.2 to 3.0.0. Current PostGIS version is like below. SELECT postgis_full_version(); postgis_full_version --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- POSTGIS="3.0.0 r17983" [EXTENSION] PGSQL="120" GEOS="3.8.0-CAPI-1.13.1 " PROJ="Rel. 5.2.0, September 15th, 2018" GDAL="GDAL 2.4.4, released 2020/01/08" LIBXML="2.9.1" LIBJSON="0.13.1" LIBPROTOBUF="1.3.2" WAGYU="0.4.3 (Internal)" RASTER (raster lib from "2.5.2 r17328" need upgrade) [UNPACKAGED!] (raster procs from "2.5.2 r17328" need upgrade) (1 row) Although most of our databases do not use raster functions, a database is using raster functions. I found upgraded databases on PostGIS3.0 is working very well apart from a database which is using postgis_raster. I tried to search the solution on how to upgrade postgis_raster, but I could not find any information about it. It is maybe some particular problem of RDS, I don't know... I found a information on AWS Developer Forum, someone faced the same error..but there is no solution on the site. https://forums.aws.amazon.com/thread.jspa?messageID=938665 Does anyone have a similar experience of this error? If so, I want to get some advice on how to solve it.. Best Regards, Jin Igarashi
_______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/postgis-users
