Database server kill thread

[dap42]

If I run the query select st_setUpperLeft(rast,st_upperLeftx( r.rast), st_upperLefty(r.rast)) from windproc , (select rast from rtab limit 1) r; in psql -d windproc PSQL drops the connection Looking at the postgresql log, gives ie the database thread dies. No user call should be able to kill a database. select st_upperLeftx(rast), st_upperLefty(rast) from rtab; Works as expected As does select st_setUpperLeft(cr.rast,st_upperLeftx( r.rast), st_upperLefty(r.rast)) from colour_ras cr, (select rast from rtab limit 1) r; windproc=# \d windproc;

Table "public.windproc"

Column | Type | Collation | Nullable | Default

---

id | integer | | not null | nextval('windproc_id_seq'::regclass) lat | real | | | lon | real | | | uwnd | real | | | vwnd | real | | | angle | real | | | speed | real | | | reading_time | timestamp with time zone | | | geom | geometry(Point,4326) | | | new_lon | real | | | new_lat | real | | |

Indexes:

"windproc_pkey" PRIMARY KEY, btree (id) "idx_reading_time" btree (timezone('UTC'::text, reading_time)) "windproc_id_idx" btree (id)

Windproc is

2024-03-08 13:46:21.877 GMT [2420] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.020 s, sync=0.007 s, total=0.078 s; sync files=2, longest=0.004 s, average=0.004 s; distance=0 kB, estimate=0 kB; lsn=2/474B8D58, redo lsn=2/474B8D20 2024-03-08 19:16:27.674 GMT [2420] LOG: checkpoint starting: time 2024-03-08 19:16:28.983 GMT [15501] dp42@windproc LOG: could not send data to client: Broken pipe 2024-03-08 19:16:28.983 GMT [15501] dp42@windproc STATEMENT: select st_setUpperLeft(rast,st_upperLeftx( r.rast), st_upperLefty(r.rast)) from windproc , (select rast from rtab limit 1) r; 2024-03-08 19:16:28.983 GMT [15501] dp42@windproc FATAL: connection to client lost 2024-03-08 19:16:28.983 GMT [15501] dp42@windproc STATEMENT: select st_setUpperLeft(rast,st_upperLeftx( r.rast), st_upperLefty(r.rast)) from windproc , (select rast from rtab limit 1) r; 2024-03-08 19:16:31.817 GMT [2420] LOG: checkpoint complete: wrote 41 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.043 s, sync=0.026 s, total=4.146 s; sync files=34, longest=0.010 s, average=0.001 s; distance=181 kB, estimate=181 kB; lsn=2/474E6450, redo lsn=2/474E6418

postgres version PostgreSQL 16.2 (Ubuntu 16.2-1.pgdg23.10+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-4ubuntu3) 13.2.0, 64-bit

POSTGIS="3.4.2 c19ce56" [EXTENSION] PGSQL="160" GEOS="3.12.0-CAPI-1.18.0" PROJ="9.2.1 NETWORK_ENABLED=OFF URL_ENDPOINT=​https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.db" GDAL="GDAL 3.7.1, released 2023/07/06" LIBXML="2.9.14" LIBJSON="0.17" LIBPROTOBUF="1.4.1" WAGYU="0.5.0 (Internal)" (core procs from "3.4.1 ca035b9" need upgrade) RASTER (raster procs from "3.4.1 ca035b9" need upgrade)

[robe]

Looks like you are running out of data scripts.

Can you run

SELECT postgis_extensions_upgrade();

To bring your scripts up to date. I doubt that is the issue, but I have seen this kind of problem for example when someone is running a 3.2 scripts against 3.3 libs.

Also if you can provide a sample of data to replicate that would help.

For what it's worth, I can't run your example because your rast's aren't full qualified so there is an ambiguous reference.

I had to change to:

select st_setUpperLeft(windproc.rast,st_upperLeftx( r.rast), st_upperLefty(r.rast)) from windproc , (select rast from rtab limit 1) r;

But can't replicate your issue.