[PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString

[PostGIS]

#5667: Performance Postgis Topolgy when adding millions by using
TopoGeo_AddLineString
--------------------------------+-------------------------
  Reporter:  Lars Aksel Opsahl  |      Owner:  strk
      Type:  enhancement        |     Status:  new
  Priority:  medium             |  Milestone:
 Component:  topology           |    Version:  3.4.x
Resolution:                     |   Keywords:  performance
--------------------------------+-------------------------
Changes (by strk):

 * keywords:   => performance

Comment:

 I agree about having more batch-loading functions, in general. Such
 function could be taking a generic geometry and was indeed forseen
 already:
 https://git.osgeo.org/gitea/postgis/postgis/src/branch/master/topology/sql/populate.sql.in#L725

 It was planned at least since 2.0.0:
 https://git.osgeo.org/gitea/postgis/postgis/src/tag/2.0.0/topology/sql/populate.sql.in.c#L1057

 In the planned form it had no return, while the implemented functions each
 return a set of identifiers of primitives corresponding to the incoming
 lines. Returning primitives helps in building TopoGeometry objects.

 Your idea of taking an array of lines might help with matching back such a
 sets of primitives to the input geometry they would belong to, so maybe
 the return code of your suggested signature could be a TopoElementArray[]
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5667#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.