[PostGIS] #5990: Adding 2 lines to Postgis topology takes 2 hours in a production line we have

[PostGIS]

#5990: Adding 2 lines to Postgis topology takes 2 hours in a production line we
have
--------------------------------+---------------------------
  Reporter:  Lars Aksel Opsahl  |      Owner:  strk
      Type:  enhancement        |     Status:  reopened
  Priority:  medium             |  Milestone:  PostGIS 3.6.1
 Component:  topology           |    Version:  3.6.x
Resolution:                     |   Keywords:
--------------------------------+---------------------------
Comment (by Lars Aksel Opsahl):

 If we compare the resulting edge the from select
 ST_Snap(line1,line2,1e-07) we also see that it's added many extra points
 because I assume that's because snapToGrid is used so all points are moved
 in postgis topology.

 Could another way off doing when you define a Topology with zero Tolerance
 then use only use ST_Snap(line1,line2,1e-07) .

 This  means that the first line is added with no changes because there are
 no lines to snap to. The second line is then added by using
 ST_Snap(line1,topology.edge,1e-07) because there is existing edge close by
 to snapto when calling addLineString with tolerance 1e-07.

 Another thing with is approach is also that we adjust input lines
 according already added data in a very clear way and not try change
 already added edges.

 Is it hard to create branch where we can test this approach ?
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5990#comment:8>
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.