pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: snorrib@gmail.com
Subject: BUG #18592: rt_raster_to_gdal: Could not load the output GDAL driver after unsuccessful paralell operation
Date: Tue, 27 Aug 2024 10:45:04 +0000
Message-ID: <18592-199eb66d64f99a51@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      18592
Logged by:          Snorri Bergmann
Email address:      snorrib@gmail.com
PostgreSQL version: 16.4
Operating system:   Linux
Description:        

We are using 16.4 with PostGIS 3.4.
Recently a DB was migrated from 9.6 to 16.4 using pg_dump.

Occasionally (once a day or every other day) an application stops working.
In the Postgres log the following is repeated:

2024-08-27 08:47:04.787 UTC [3925026] ERROR:  rt_raster_to_gdal: Could not
load the output GDAL driver
2024-08-27 08:47:04.787 UTC [3925026] CONTEXT:  PL/pgSQL function
st_aspng(raster,text[]) line 31 at RETURN
2024-08-27 08:47:04.787 UTC [3925026] STATEMENT:
                    SELECT
                        ST_AsPNG(ST_ColorMap(ST_TRANSFORM(rast, 3857),
...........................

2024-08-27 08:47:04.787 UTC [3924754] ERROR:  rt_raster_to_gdal: Could not
load the output GDAL driver
2024-08-27 08:47:04.787 UTC [3924754] CONTEXT:  PL/pgSQL function
st_aspng(raster,text[]) line 31 at RETURN
etc. etc.

The errors persist until this is executed (which fixes the issue temporarily
at least):
ALTER DATABASE mydb SET postgis.gdal_enabled_drivers TO 'GTiff PNG JPEG';
ALTER SYSTEM SET postgis.gdal_enabled_drivers TO 'ENABLE_ALL';
SELECT pg_reload_conf();

The first  driver error is always preceded by this:
2024-08-27 08:47:04.546 UTC [3925026] WARNING:  cannot set parameters during
a parallel operation
2024-08-27 08:47:04.546 UTC [3925026] CONTEXT:  SQL function "st_transform"
statement 1
2024-08-27 08:47:04.546 UTC [3924754] WARNING:  cannot set parameters during
a parallel operation
2024-08-27 08:47:04.546 UTC [3924754] CONTEXT:  SQL function "st_transform"
statement 1
        parallel worker
And then the driver errors appear repeatedly:
2024-08-27 08:47:04.787 UTC [3925026] ERROR:  rt_raster_to_gdal: Could not
load the output GDAL driver
.
.
.



Message-ID: <18592-199eb66d64f99a51@postgresql.org>
Permalink:  ../18592-199eb66d64f99a51@postgresql.org/
Also on:    postgresql.org/message-id/18592-199eb66d64f99a51@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, snorrib@gmail.com
  Subject: Re: BUG #18592: rt_raster_to_gdal: Could not load the output GDAL driver after unsuccessful paralell operation
  In-Reply-To: <18592-199eb66d64f99a51@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox