[Tile-serving] [openstreetmap/osm2pgsql] Non moving node updates should not update related way/relation geometries (#1046)

[Jochen Topf]

@cquest Can you elaborate on what you tested exactly and how the numbers changed with and without this patch? There are several issues here that could affect timing: With the patch fewer ways (and relations) will be marked as (possibly) changed. On the other hand we have to lookup the old location of all nodes, which is cheap if we are using flat node store, but possibly expensive when using the database. All of this, of course, depends on what kind of node changes there are usually.

To figure out the best way to do this we need some numbers not from isolated queries, but from real-world update runs. Does this, on avarage, speed up things considerably or not? How does the flat node factor in here? How does the [bucket index](https://github.com/openstreetmap/osm2pgsql/blob/master/docs/bucket-index.md)? @cquest You speek of a 10% speed up which would be well worth it, but I am not sure what you have been measuring there.

-- 
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/issues/1046#issuecomment-712658434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20201020/4e4d96a0/attachment.htm>