[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:
--------------------------------+-------------------
Comment (by strk):

 I believe there is a 1:1 ratio between calls to `TopoGeo_addLinestring`
 and queries to topology.topology table. That same query also serves the
 purpose of fetching the OID of the geometry type, which is why the
 null::geometry part is in there.

 Implementation of a cache would result in a single query per session, or
 per transaction, while taking a topology.topology record would still miss
 the geometry oid extraction that would then need to be still performed on
 a 1:1 ratio.

 For this reason I'm thinking the best performance improvement here would
 be to implement a cache or the batch-loading function which would have
 similar effects. The cache would not require any change in the client
 code, which makes the performance improvement transparent to the users.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5667#comment:14>
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.