[Tile-serving] [openstreetmap/osm2pgsql] Add an option to TRUNCATE instead of DROP CASCADE when --create option set (#758)

[Frederik Ramm]

It is a niche requirement because only people creating views will have that requirement, and that is not part of the usual osm2pgsql usage scenario. It would cause errors if used by someone who doesn't know exactly what they are doing, and where osm2pgsql then attempts to load data into a table that does not have the expected data format. Plus, it would not work anyway, as @pnorman has explained above; you would have to modify not only the TRUNCATE portion but also the sorting afterwards. Finally, to make this remotely efficient you would have to first drop/disable existing indexes. So it is a lot of changes for a use case that benefits very people. It is perhaps something you should make your own special "osm2pgsql with improved matview suport" fork for.

-- 
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/758#issuecomment-533881765
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20190922/50902303/attachment.html>