[Tile-serving] [openstreetmap/osm2pgsql] Quick fix for problem with updating data in flex backend (#1140)

[Jochen Topf]

Under some circumstances when using the two-stage processing of the flex
backend data was not updated correctly. This happens when a way changes
that is in a relation and that relation has another way in common with
a different relation.

The solution for this is introducing a stage1c processing, which this
commit does in a really hacky way. To do this cleanly we need to
refactor a lot of the middle and id_tracker code.

Processing happens in these stages:

* stage 1a: Read input file and process all objects in it.
* stage 1b: Process dependent objects of objects from 1a (ie changed
  nodes trigger changes in ways with those nodes, changes in all
  objects potentially trigger changes in relations).
* stage 1c: Process dependent objects (currently only relations) of
  objects marked during stage 1a/1b (this one is new). No more marking
  is done in stage 1c.
* stage 2: Process objects marked in stage 1a or 1b.
You can view, comment on, or merge this pull request online at:

  https://github.com/openstreetmap/osm2pgsql/pull/1140

-- Commit Summary --

  * Quick fix for problem with updating data in flex backend

-- File Changes --

    M src/osmdata.cpp (24)
    M src/output-flex.cpp (51)
    M src/output-flex.hpp (18)
    M src/output.hpp (3)

-- Patch Links --

https://github.com/openstreetmap/osm2pgsql/pull/1140.patch
https://github.com/openstreetmap/osm2pgsql/pull/1140.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/pull/1140
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20200426/eb01bae9/attachment.htm>