[postgis-tickets] [PostGIS] #4684: concurrent topology construction routine may result in invalid topology (was: Topology construction routine results invalid topology)

[PostGIS]

#4684: concurrent topology construction routine may result in invalid topology
-----------------------+-------------------
  Reporter:  laopsahl  |      Owner:  strk
      Type:  defect    |     Status:  new
  Priority:  medium    |  Milestone:
 Component:  topology  |    Version:  3.0.x
Resolution:            |   Keywords:
-----------------------+-------------------
Changes (by strk):

 * owner:  pramsey => strk
 * component:  postgis => topology


Comment:

 There might be a way, using PostgreSQL locks, to reduce the chances (or
 completely avoid) that such invalidities are introduced in the topology.
 Serializing access to the topology primitives could be overkill becuase it
 would prevent the 3 steps approach above. What we want to avoid is that
 more than ONE transaction at the time works on the same edges. Row level
 locks might help with that: https://www.postgresql.org/docs/10/explicit-
 locking.html#LOCKING-ROWS

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