openmaptiles

History

Use pg_trigger_depth to avoid re-trigger in update (#1708 )

Some of the `update_osm_${LAYER}`-functions, which are executed by triggers on updates, execute an UPDATE statement on the same tables that have these triggers. This causes the trigger functions `flag` and `store` to run multiple times for one record. 

For instance, if I add log in the trigger functions and run an INSERT on `osm_housenumber_point`, this output is generated:  

```
NOTICE:  Store
NOTICE:  Flag
NOTICE:  Refresh housenumber
NOTICE:  Flag
NOTICE:  Store
NOTICE:  Flag
INSERT 0 1
```

If we limit the triggers from executing if they are called from another trigger using `pg_trigger_depth() < 1`, the triggers will only be triggered once per record:

```
NOTICE:  Store
NOTICE:  Flag
NOTICE:  Refresh housenumber
INSERT 0 1
```

This will prevent redunant executions and might improve update performance.  

Co-authored-by: Patrik Sylve <patrik.sylve@t-kartor.com>

2025-02-18 11:18:04 +01:00

etl_diagram.png

Upgrade to omt-tools v6, Imposm 0.11.1 and migrate SQL (#1246 )

2021-10-14 11:38:28 -04:00

housenumber_centroid.sql

Use pg_trigger_depth to avoid re-trigger in update (#1708 )

2025-02-18 11:18:04 +01:00

housenumber_display.sql

Fix housenumber_display.sql - cast to bigint instead of integer. (#1637 )

2024-02-26 13:04:00 +01:00

housenumber.sql

Convert semi-colon separated house numbers to a range (#1562 )