pnorman left a comment (osm2pgsql-dev/osm2pgsql#2407)
I've looked into something other than delete/copy a few times and the problem I
always run into is the lack of primary key.
Conceptually the problem is a bit broader, because an OSM object can result in
one or multiple database rows, and the number of rows can change in an update.
Because a modify can change the number of rows we **have** to use an insert or
delete somewhere behind the scenes. I don't see that a custom function would
help either, since the database triggers are still going to catch the insert
and delete.
If you have a primary key it becomes fairly easy - all inserts and
modifications in append mode become an `INSERT ... ON CONFLICT ...`
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/issues/2407#issuecomment-3215754317
You are receiving this because you are subscribed to this thread.
Message ID: <osm2pgsql-dev/osm2pgsql/issues/2407/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
