unable to use postgis_raster extension: GDAL Drivers Disabled
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- postgresql
- Domain
- databases
Research direction
The reported entry points are CREATE EXTENSION postgis_raster, SELECT PostGIS_Full_Version(), and ST_FromGDALRaster; begin by reproducing the SQL setup with the stated PostgreSQL 15, PostGIS 3.3.2, and GDAL 3.8.5 versions. Done means identifying why GDAL drivers are disabled or superuser access is required and confirming that the raster insert succeeds.
Written by the indexing model from the issue text.
Description
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
I am working with large climate datasets and need to optimize using PostGIS Raster. Both PostGIS and PostGIS_Raster extensions are enabled, as confirmed by SELECT PostGIS_Full_Version(), which indicates proper versions for PostGIS, GDAL, and Raster. However, when attempting to insert raster data using ST_FromGDALRaster, I encounter the error rt_util_gdal_open: Cannot open file. All GDAL drivers disabled, suggesting that GDAL drivers are not correctly enabled despite proper setup. I'm also unable to enable the extensions w/o superuser permission
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Steps to Reproduce
- Setup PostgreSQL and PostGIS:
• Install PostgreSQL 15 and PostGIS 3.3.2.
• Ensure GDAL (version 3.8.5 or compatible) is installed. - Enable PostGIS and Raster Extensions:
CREATE EXTENSION postgis;
CREATE EXTENSION postgis_raster;
- Check PostGIS Version:
Run the following query to confirm PostGIS and GDAL are properly installed:
SELECT PostGIS_Full_Version();
getting:
POSTGIS="3.3.2" [...] GDAL="GDAL 3.8.5" [...] RASTER
- Create a Table for Raster Data:
CREATE TABLE __gpcp_precip (
time TIMESTAMP PRIMARY KEY,
rast RASTER
);
- Attempt to Insert Raster Data:
Use the following query with appropriate values:
INSERT INTO __gpcp_precip (time, rast)
VALUES ('2024-12-01 00:00:00', ST_FromGDALRaster('/path/to/raster.tif'))
ON CONFLICT (time) DO UPDATE
SET rast = EXCLUDED.rast;
- Error Encountered:
The error rt_util_gdal_open: Cannot open file. All GDAL drivers disabled is thrown.
Expected behavior
data is inserted
Additional context
Add any other context about the problem here.
- Dominant language
- Nix
- Stars
- 1.8k
- Forks
- 266
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 25
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/postgres
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
`supabase/postgres:17.6.1.105` (amd64) — backend SIGSEGV during a heavy pgTAP file, CI-CPU-specific Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in supabase/postgres
Similar issues
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
[BUG] A column whose default is the empty string is drawn in the ER diagram as having no default Openbug database-provider good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
libredb/libredb-studio#1030 · 6 comments ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug redshift
Difficulty 2/5 1-3 hours Newbie friendliness 88/100