[postgis-tickets] [PostGIS] #4282: ST_LineToCurve hangs indefintely

[PostGIS]

#4282: ST_LineToCurve hangs indefintely
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  blocker  |  Milestone:  PostGIS 3.0.0
 Component:  postgis  |    Version:  trunk
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 Okay I just tested this on my production PostgreSQL 11


 {{{
 PostgreSQL 11.1, compiled by Visual C++ build 1914, 64-bit
 POSTGIS="2.5.1 r17027" [EXTENSION] PGSQL="110" GEOS="3.7.0-CAPI-1.11.0
 3.7.1" PROJ="Rel. 4.9.3, 15 August 2016" GDAL="GDAL 2.2.4, released
 2018/03/19" LIBXML="2.7.8" LIBJSON="0.12" LIBPROTOBUF="1.2.1" (core procs
 from "2.5.0 r16836" need upgrade) RASTER (raster procs from "2.5.0 r16836"
 need upgrade)
 }}}

 and it returned answers within 100ms.

 I tested it on my PostgreSQL 11 mingw setup against an earlier PostGIS 3.0
 and it again returned answers in < 100ms.


 {{{
 PostgreSQL 11.0 on x86_64-w64-mingw32, compiled by gcc.exe (x86_64-posix-
 seh-rev0, Built by MinGW-W64 project) 8.1.0, 64-bit POSTGIS="3.0.0dev
 r16983" PGSQL="94" (procs need upgrade for use with "110")
 GEOS="3.7.0-CAPI-1.11.0 673b9939" PROJ="Rel. 5.2.0, September 15th, 2018"
 GDAL="GDAL 2.3.1, released 2018/06/22" LIBXML="2.7.8" LIBPROTOBUF="1.2.1"
 (core procs from "2.4.6 r17057" need upgrade) RASTER (raster procs from
 "2.4.6 r17057" need upgrade)
 }}}

 So this does appear to be a recent development.  Still haven't nailed it
 down to PostGIS or PostgreSQL at fault yet.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4282#comment:2>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.