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


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

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4684, comment 13

    v1 v2  
    11A test case showing how to use row level lock to avoid Topology errors .
    22
    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 **
     3Info from the db_topo_rowlevel_lock_readme.txt in file db_topo_rowlevel_lock.zip.
    54
    6 So the only problem we here are when multiple threads working with related spatial areas, which are expected.
     5# Create a empty database
     6
     7
     8{{{
     9psql postgres -c'create database t1'
     10
     11}}}
     12# Add the code needed for testing
     13
     14
     15{{{
     16t1 -f db_topo_rowlevel_lock_init.sql
     17
     18}}}
     19# Test with no rowlevel locking, should return something like this
     20
     21
     22{{{
     23psql t1 -f db_topo_rowlevel_lock_test_fail.sql
     24 ?column?  |      error       | id1 | id2
     25------------+------------------+-----+-----
     26 validation | face within face |   1 |   2
     27 validation | face within face |   2 |   1
     28 validation | face within face |   1 |   3
     29 validation | face within face |   2 |   3
     30(4 rows)
     31
     32}}}
     33# Test with rowlevel locking , no topop errors should be found
     34
     35
     36{{{
     37psql t1 -f db_topo_rowlevel_lock_test_ok.sql
     38
     39}}}