[postgis-tickets] [PostGIS] #2083: ST_RemEdgeModFace performance review

[PostGIS]

#2083: ST_RemEdgeModFace performance review
--------------------------+-----------------------------
  Reporter:  strk         |      Owner:  strk
      Type:  enhancement  |     Status:  reopened
  Priority:  medium       |  Milestone:  PostGIS Fund Me
 Component:  topology     |    Version:  2.0.x
Resolution:               |   Keywords:  performance
--------------------------+-----------------------------
Changes (by strk):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 relation(layer_id) should not be needed because you usually don't have
 those many layers and anyway the btree (layer_id, topogeo_id, element_id,
 element_type) index would be already used when a query using layer_id is
 issued.

 The abs(element_id) I removed the need for in
 [854103fa2e087b53485c8cf403a1fcb952146be2/git]

 relation(topogeo_id) would also be covered by the existing btree on all
 members, as topogeo_id is second member after layer_id, and you always
 search for topogeo_id togheter with layer_id.

 The edge_data(geom) is already created.

 The node(containing_face) I pushed already with
 [e4495fb792fe31a87a84e92297d276baf254007a/git]

 The only left over are the indices on abs_next_{left,right}_edge which I
 guess would be useful upon deleting edges, to re-link the edges pointing
 to the one being removed. I'm reopening the ticket to research upon this
 one.

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