[OSM-dev] speeding up loading an OSM dump into PostGIS?

Frederik Ramm frederik at remote.org
Fri Dec 16 11:52:14 GMT 2011


On 12/16/11 12:49, Peter Körner wrote:
>> with the SQL command execution, especially the index creation, being
>> the most expensive part of an osm2pgsql run this would onyl save about
>> 1/4 to 1/3 of the total planet import execution time i'm afraid ...
> It would help with keeping updated: you would not need the --slim tables
> anymore (on each server - only on the master)

At the cost of high network traffic - a single node moved in the outline 
of the Germany polygon would mean that a geometry with tens of thousands 
of points would have to be pushed from the master to the clients.


More information about the dev mailing list