Fwd: Postgres segfaults on raster query

Gandalf the Gray pjduplooy.gis at gmail.com
Thu Jan 18 21:40:11 PST 2024


---------- Forwarded message ---------
From: Gandalf the Gray <pjduplooy.gis at gmail.com>
Date: Fri, Jan 19, 2024 at 7:39 AM
Subject: Re: Postgres segfaults on raster query
To: Paul Ramsey <pramsey at cleverelephant.ca>


Hi Paul.

I may be completely off base here, but MobilityDB requires you to have
postgis in preload.  From their github:

"You should also set the following in postgresql.conf depending on the
version of PostGIS you have installed (below we use PostGIS 3):

shared_preload_libraries = 'postgis-3'
max_locks_per_transaction = 128

If you do not preload the PostGIS library you will not be able to load the
MobilityDB library and will get an error message such as the following one

ERROR:  could not load library
"/usr/local/pgsql/lib/libMobilityDB-1.0.so": undefined symbol:
ST_Distance"


On Fri, Jan 19, 2024 at 6:26 AM Paul Ramsey <pramsey at cleverelephant.ca>
wrote:

> This seems… odd to me? In what context is putting postgis into the preload
> a requirement?
>
> P
>
> > On Jan 18, 2024, at 8:20 PM, Scott <public at postholer.com> wrote:
> >
> > Bam!
> >
> > That was it. Thanks Regina, you rock!
> >
> > On 1/18/24 20:16, Regina Obe wrote:
> >> ALTER SYSTEM  SET shared_preload_libraries = 'postgis-3';
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20240119/4b55c801/attachment.htm>


More information about the postgis-users mailing list