Hi, I haven't tried setting up the constraints after the import, hence why I have left it for someone else to comment on it.
Shaun On 13 Apr 2013, at 07:42, Jeff Meyer <[email protected]> wrote: > Shaun - your answer is helpful, but does it answer Martin's question? > > Would it be better to set up the indexes and constraints after the import? > Does it matter? > > Thanks, Jeff > > On Tue, Apr 2, 2013 at 1:38 PM, Shaun McDonald <[email protected]> > wrote: > Hi, > > Changing some of the parameters for the Postgres database can help speed up > the import in a similar manner to those settings for a Mapnik import. > > Shaun > > On 2 Apr 2013, at 19:58, Martin Schafran <[email protected]> wrote: > > > > > hi, > > > > im trying to install my own osm server with api 0.6. > > > > following instructions i stuck on database import. > > > > http://wiki.openstreetmap.org/wiki/Rails_port#Database_tables > > > > at this point all indexes and constraints are created before import. > > > > Is this really the correct approach? indexes and constraints make import > > slow. > > > > btw. i got 'duplicate key value violates unique constraint > > "current_nodes_pkey1" > > Detail: Key (id)=(12) already exists.' > > > > :-O source is geofabrik germany extract. > > > > > > martin > > > > _______________________________________________ > > dev mailing list > > [email protected] > > http://lists.openstreetmap.org/listinfo/dev > > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev > > > > -- > Jeff Meyer > Global World History Atlas > www.gwhat.org > [email protected] > 206-676-2347 > > OpenStreetMap: Mapping with a Human Touch > osm: Open Historical Map (OHM) / my OSM user page > t: @GWHAThistory > f: GWHAThistory > > >
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
