[postgis-devel] PostGIS 3.2.0beta3 is released

[Regina Obe]

Greg,
[Regina Obe] 
Thanks for the testing.

> My memory of previous version tests is that they basically work, except
> there is a raster crash, which has been happening for a long time.  This
time, I
> got a crash in geography:
> 
> PostgreSQL 10.18 on x86_64--netbsd, compiled by gcc (nb3 20190319) 7.4.0,
> 64-bit
>   Postgis 3.2.0beta3 - (1a89e36) - 2021-12-05 01:26:39
>   scripts 3.2.0beta3 1a89e36
>   raster scripts 3.2.0beta3 1a89e36
>   GEOS: 3.10.1-CAPI-1.16.0
>   PROJ: 6.3.2
>   GDAL: GDAL 3.4.0, released 2021/11/04
> 
>    ./regress/core/geography ..Died at /tmp/work/databases/postgresql-
> postgis2/work/postgis-3.2.0beta3/regress/run_test.pl line 744.
>    failed (psql exited with an error: /tmp/pgis_reg/test_19_out)
> 
> and test_19_out, timestamp 20:31:28 2021
> 
>   psql:geography.sql:11: server closed the connection unexpectedly
>           This probably means the server terminated abnormally
>           before or while processing the request.
>   psql:geography.sql:11: connection to server was lost
> 
[Regina Obe] 
Line 11 corresponds to query below.  I don't think we've touched that area
of geography in any way that is 
hasn't been touched in 3.1.4 and your 3.1.4 works fine?


SELECT c, abs(ST_Distance(ply::geography, pt::geography) -
_ST_DistanceUnCached(ply::geography, pt::geography)) < 0.01 FROM
( VALUES
('geog_distance_cached_1a', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))',
'POINT(5 5)'),
('geog_distance_cached_1b', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))',
'POINT(5 5)'),
('geog_distance_cached_1c', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))',
'POINT(5 5)'),
('geog_distance_cached_1e', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))',
'POINT(5 5)'),
('geog_distance_cached_1f', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))',
'POINT(5 5)'),
('geog_distance_cached_1g', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))',
'POINT(5 5)'),
('geog_distance_cached_1h', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))',
'POINT(5 5)')
) AS u(c,ply,pt);


Is it possible to get a gdb backtrace of this query and confirm you can
consistently trigger the issue?