Thanks for the tip! I found the root of the problem.
When I ran pg_config it returned config info for pg 15. That's great,
but this db is running on pg 13!
Not long ago, apt upgrade added pg 15, which I did not want. I thought I
removed, purged it. Apparently not.
I just physically moved
> 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 wrote:
> >
> > Bam!
> >
> > That was it. Thanks Regina, you rock!
> >
> > On 1/18/24 20:16, Regina Obe wrote:
> >> ALTER SYSTEM SET
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 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';
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';
> Here's what's happening:
>
> psql -d mydb
>
> select rid from rastertable where rid = 1;
>
> Psql connection drops, postgres segfaults and restarts.
>
> BUT, if I do a query such as this FIRST:
>
> select postgis_full_version();
>
> Then do other raster queries, it works fine. I suspect I
You aren’t even hitting the raster subsystem… your target list is rid and your
filter is rid… so…?
I’d guess you have a seriously borked install, somehow.
P
> On Jan 18, 2024, at 5:02 PM, Scott wrote:
>
> Here's what's happening:
>
> psql -d mydb
>
> select rid from rastertable where rid =
