[postgis-tickets] [PostGIS] #3792: ST_3DIntersects not marked as parallel safe

[PostGIS]

#3792: ST_3DIntersects not marked as parallel safe
---------------------+---------------------------
 Reporter:  robe     |      Owner:  robe
     Type:  defect   |     Status:  assigned
 Priority:  medium   |  Milestone:  PostGIS 2.3.4
Component:  postgis  |    Version:  2.3.x
 Keywords:           |
---------------------+---------------------------
 As paranoidd noted on irc:


 {{{
 13:52:20        paranoidd:      hi, folks!
 13:53:41        paranoidd:      PostGIS newbie here, with a question
 that's possibly been answered before
 13:54:44        paranoidd:      so, I've been looking into some query
 plans and I realized that some of them involving ST_3DIntersects() were
 serializing the plan through sequential scans
 13:55:15        paranoidd:      ST_Intersects(), on the other hand,
 benefits from parallel scans
 13:55:44        paranoidd:      it looks like ST_Intersects() is marked
 PARALLEL SAFE, whereas ST_3DIntersects() is not
 13:58:38        paranoidd:      I see that
 https://trac.osgeo.org/postgis/ticket/3650 marks certain aggregate
 functions as parallel safe, so I wonder if (1) the dev team has already
 gone through a review of ST_3DIntersects() and realized that it's not
 parallel safe, or (2) a thorough review of this function is still pendi
 }}}


 I don't think there is any reason why we shouldn't mark as parallel safe.
 This needs to be done for both regular postgis and SFCGAL.

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