Hello,
I am trying to get a workaround for the problem below.
extension "postgis_raster" has no installation script nor update path for version "unpackaged"
see more details in this link
https://trac.osgeo.org/postgis/ticket/5222#ticket
Have you encountered this issue before? If yes, do you know how to fix it ?
Thanks,
| Marcelo Marques | Esri PS Products | Principal Product Engineer |
Marcelo,
Apologies, this file was left out in my packaging. I’ll create an updated package later this week to fix this issue and will also have a 3.3.0 which doesn’t have this issue.
I’ve updated ticket to reflect.
Copy the attached file (which is essentially an empty file) into your
C:\Program Files\PostgreSQL\11\share\extension folder
And then try your upgrade again.
Sorry for the omission,
Regina
_______________________________________________
postgis-users mailing list
postgi...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users
Oh you are running 3.2.2 and not 3.2.3. I know 3.2.3 has this file
postgis_raster--unpackaged--3.2.3.sql
which is what you are missing.
Can you install 3.2.3? Then once you install the binaries, run again and it should work.
I guess my attachment was too big.
Here is a link to it if you need it, https://winnie.postgis.net/download/windows/pg11/buildbot/extras/postgis--unpackaged--3.2.2.sql
but if you are running a patched PostgreSQL 11, you’ll really need to be using the PostGIS 3.2.3 install which you can get from application stackbuilder or https://download.osgeo.org/postgis/windows/pg11/
Hope that helps,
Regina
From: Regina Obe [mailto:l...@pcorp.us]
Sent: Tuesday, August 30, 2022 8:00 PM
To: 'PostGIS Users Discussion' <postgi...@lists.osgeo.org>
Subject: RE: [postgis-users] extension "postgis_raster" has no installation script nor update path for version "unpackaged"
Attached is the one for 3.2.2
But that is in my artifacts so should have already been installed by your setup. Do you have the attached file in your share/extension folder?
From: Regina Obe [mailto:l...@pcorp.us]
Sent: Tuesday, August 30, 2022 7:56 PM
To: 'PostGIS Users Discussion' <postgi...@lists.osgeo.org>
Subject: RE: [postgis-users] extension "postgis_raster" has no installation script nor update path for version "unpackaged"
Oh you are running 3.2.2 and not 3.2.3. I know 3.2.3 has this file
postgis_raster--unpackaged--3.2.3.sql
which is what you are missing.
Can you install 3.2.3? Then once you install the binaries, run again and it should work.
From: postgis-users [mailto:postgis-us...@lists.osgeo.org] On Behalf Of Marcelo Marques
Sent: Tuesday, August 30, 2022 7:39 PM
To: PostGIS Users Discussion <postgi...@lists.osgeo.org
>
Marcelo,
I think it’s your query and below behavior you describe as I understand it seems correct.
And your output is correct:
"POSTGIS=""3.2.3 3.2.3"" [EXTENSION] PGSQL=""110"" GEOS=""3.10.3-CAPI-1.16.1"" PROJ=""7.2.1""
GDAL=""GDAL 3.4.3, released 2022/04/22 GDAL_DATA not found""
LIBXML=""2.9.9"" LIBJSON=""0.12"" LIBPROTOBUF=""1.2.1"" WAGYU=""0.5.0 (Internal)"" RASTER"
Instead of:
SELECT * FROM pg_available_extensions WHERE name LIKE 'postgis';
Should be:
SELECT * FROM pg_available_extensions WHERE name LIKE 'postgis%';
And then the postgis_raster should show along with postgis_topology and postgis_sfcgap and postgis_tiger_geocoder.
Is this a different database?
I thought your other one showed raster fully installed and on version 3.2.3.
Try doing:
CREATE EXTENSION postgis_raster VERSION 'unpackaged';
ALTER EXTENSION postgis_raster UPDATE;
Well if you did that, you destroyed all your raster data anyway.
If you had no raster data, then just run the uninstall_rtpostgis.sql
Which is located in – C:\Program Files\PostgreSQL\11\share\contrib\postgis-3.2\ uninstall_rtpostgis.sql
That should clean up the mess and allow you to do regular after if you still want the extension.
CREATE EXTENSION postgis_raster;
If you did have raster data, then you’d need to restore that from backup. If many tables, probably the cleanest is to
1) Create a new database and do: CREATE EXTENSION postgis; CREATE EXTENSION postgis_raster;
2) Then restore your database backup into this new database.
Note for cases where you have raster data and need to restore from backup, you need to do CREATE EXTENSION postgis_raster; since that won’t be in your backup and would fail restore if it can’t find the raster type.
For databases with only vector, then doing a restore without running any CREATE EXTENSION should work fine, since CREATE EXTENSION postgis; would be included in your backup.