[postgis-tickets] [PostGIS] #4919: SQL reliably crashes Server

[PostGIS]

#4919: SQL reliably crashes Server
----------------------+---------------------------
  Reporter:  Robins   |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 3.1.3
 Component:  postgis  |    Version:  3.0.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 adding Tom Lane's comment for completeness.


 {{{
 The trace shows that gserialized_datum_get_gidx_p is passing a NULL
 datum pointer to pg_detoast_datum_slice.  Whether the slice length
 is appropriate seems like an academic question.


 (It does look like that code validates sliceoffset and slicelength
 and does something appropriate if they're outside the bounds of
 the datum's size.  But you gotta have a datum.)
 }}}

 and for my testing I was testing against 3.1.2dev (just before release
 against PostgreSQL 13)


 For testing with pg14dev, PostGIS 3.2.0dev, the query does not run,

 Complains that
 {{{
  operator does not exist: point @ lseg
 }}}

 Indeed if I run this query in PostgreSQL 14


 {{{
 SELECT cast(NULL AS point) @(SELECT NULL::lseg LIMIT 0)
 }}}

 I get the same error so I guess they took out the @ operator in PostgreSQL
 14 for point @ lseg.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4919#comment:7>
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.