[postgis-tickets] [PostGIS] #4684: concurrent topology construction routine may result in invalid topology

[PostGIS]

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

Comment (by strk):

 For the two cases above there's no row to be locked because the problem is
 with rows yet to be visible by the other process. The only way to ensure
 objects in an area would be visible by other transaction would be to
 acquire a lock on an *area*, reguardless of objects already existing in
 the area. We could think of a special "spatial_locks" table to be created
 in each topology where each process would insert locks for "areas",
 obtainable only for areas not intersecting any other already locked area.

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