[postgis-tickets] [PostGIS] #5106: ST_RemEdgeNewFace causes postgre to core dump, but not ST_RemEdgeModFace
PostGIS
trac at osgeo.org
Mon Jan 30 06:39:41 PST 2023
#5106: ST_RemEdgeNewFace causes postgre to core dump, but not ST_RemEdgeModFace
-----------------------+---------------------------
Reporter: laopsahl | Owner: strk
Type: defect | Status: new
Priority: medium | Milestone: PostGIS 3.4.0
Component: topology | Version: 3.2.x
Resolution: | Keywords:
-----------------------+---------------------------
Comment (by strk):
So, specially built PostgreSQL version isn't needed because we're passing
0x0 pointer to pfree and that should ALWAYS segfault. But what I don't
understand is how it is possible for ST_RemEdgeNewFace to NOT find any of
the faces found in an edge's left_face and right_face columns, as those
values *should* theoretically always be checked by foreign key constraints
to match existing records in the face table.
I suspect this has to do with the way we use the "read_only" parameter to
SPI_execute, that is, has to do with visibility of data changes.
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5106#comment:5>
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.
More information about the postgis-tickets
mailing list