Changes between Initial Version and Version 1 of Ticket #4684, comment 13


Ignore:
Timestamp:
Jul 14, 2020, 11:31:26 PM (4 years ago)
Author:
Lars Aksel Opsahl

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4684, comment 13

    initial v1  
    11A test case showing how to use row level lock to avoid Topology errors .
    22
    3 Info from the db_topo_rowlevel_lock_readme.txt in file  db_topo_rowlevel_lock.zip.
     3**This does not lock like bug in Postgis Topology bug it was bug was related to missing primary key , I have now been running 60 interatins with no errors. The new correct SQL is uploaded.
     4**
    45
    5 # Create a empty database
    6 
    7 {{{
    8 psql postgres -c'create database t1'
    9 }}}
    10 
    11 # Add the code needed for testing
    12 
    13 {{{
    14 t1 -f db_topo_rowlevel_lock_init.sql
    15 }}}
    16 
    17 # Test with no rowlevel locking, should return something like this
    18 
    19 {{{
    20 psql t1 -f db_topo_rowlevel_lock_test_fail.sql
    21  ?column?  |      error       | id1 | id2
    22 ------------+------------------+-----+-----
    23  validation | face within face |   1 |   2
    24  validation | face within face |   2 |   1
    25  validation | face within face |   1 |   3
    26  validation | face within face |   2 |   3
    27 (4 rows)
    28 }}}
    29 
    30 
    31 # Test with rowlevel locking , no topop errors should be found
    32 
    33 {{{
    34 psql t1 -f db_topo_rowlevel_lock_test_ok.sql
    35 }}}
     6So the only problem we here are when multiple threads working with related spatial areas, which are expected.