<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Confirmed here. Love a good crasher.<div><a href="https://trac.osgeo.org/postgis/ticket/5793#ticket">https://trac.osgeo.org/postgis/ticket/5793#ticket</a></div><div><br></div><div>P<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Oct 9, 2024, at 8:49 AM, Fredrik Widlert <fredrik.widlert@digpro.se> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div class="gmail-nH"><div class="gmail-l2" style="padding-bottom:0px">Hi, I think I've found a segfault in PostGIS 3.5.0 and PostGIS 3.4.3 when running on PostgreSQL 17.<br><br>We have a relatively complicated query that used to work on PostgreSQL 16 with PostGIS 3.4.0 but now gives the error.<br>Instead of providing the full query, I've minimized it to a trivial version below that still gives the error.<br><br>Tested on:<br>* PostgreSQL 17 / PostGIS 3.4.3 installed through apt on Ubuntu 20.04<br>* PostgreSQL 17 / PostGIS 3.5.0 installed from source on Ubuntu 24.04<br><br><br>postgres=# select version();<br> version<br>--------------------------------------------------------------------------------------------------<br> PostgreSQL 17.0 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit<br><br>postgres=# select postgis_full_version();<br><br>POSTGIS="3.5.0 d2c3ca4" [EXTENSION] PGSQL="170" GEOS="3.12.1-CAPI-1.18.1" PROJ="9.4.0<br>NETWORK_ENABLED=OFF URL_ENDPOINT=<a href="https://cdn.proj.org/">https://cdn.proj.org</a> USER_WRITABLE_DIRECTORY=/home/postgres/.local/share/proj DATABASE_PATH=/usr/share/proj/proj.db"<br>(compiled against PROJ 9.12.1) LIBXML="2.9.14" LIBJSON="0.17" LIBPROTOBUF="1.4.1" WAGYU="0.5.0 (Internal)"<br>(1 row)<br><br><br>Test case:<br>========<br>create extension postgis;<br><br>create table tab (shape geography(GeometryZ,4326));<br><br>select st_buffer(st_collect(array_agg (tab.shape)::geometry[])::geography, 10.0) from tab;<br>========<br><br>Result:<br><br>postgres=# select st_buffer(st_collect(array_agg (tab.shape)::geometry[])::geography, 10.0) from tab;<br>server closed the connection unexpectedly<br> This probably means the server terminated abnormally<br> before or while processing the request.<br>The connection to the server was lost. Attempting reset: Failed.<br>The connection to the server was lost. Attempting reset: Failed.<br><br>Can others reproduce the same problem or did I do something wrong on my installations?<br>/Fredrik<br></div></div></div>
</div></blockquote></div><br></div></body></html>