[Tile-serving] [openstreetmap/osm2pgsql] Slow --append node processing with osm2pgsql 1.8.1 (7-8* slower than older setup) (Discussion #1971)

[wgds60]

@SomeoneElseOSM that's why I'm trying to find the cause of this slowness. Your call_pyosmium.sh example is practically doing the same --append command at osm2pgsql as done here (while I'm using a higher number of processes option).

So I rather wonder if osm2pgsql changed their requirements in regard to the diff.os.gz changes file? But I don't see anything in that regard.

Now reading through all release notes for osm2pgsql I've found this change in release 1.4.0:

"Switch multipolygon generation from default off to default on. The multi option on the area geometry transformation has been removed and there is a new option split_at."

Does this refers to multipolygon handling as discussed here: https://www.paulnorman.ca/blog/2014/03/osm2pgsql-multipolygons/ ?

If the default is now "on", how do I switch it off? The -G or --multi-geometry option does not have a value, or do I read this wrong (from the osm2pgsql manual):

"-G, --multi-geometry | Normally osm2pgsql splits multi-part geometries into separate  database rows per part. A single OSM object can therefore use several  rows in the output tables. With this option, osm2pgsql instead generates  multi-geometry features in the PostgreSQL tables."

?


 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/discussions/1971#discussioncomment-6123156
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/osm2pgsql/repo-discussions/1971/comments/6123156 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20230608/a4a87884/attachment-0001.htm>