[OSM-dev] Importing with osm2pgsql halts

Nyx nyxynyx at gmail.com
Thu Sep 13 21:14:00 BST 2012


Hi everyone! I just installed PostgreSQL 9.1, PostGIS 2 and Nominatim. I
started importing a map of the northeast of US from
http://download.geofabrik.de/osm/north-america/ using osm2pgsql 0.80.

Here's the output:

Using projection SRS 4326 (Latlong)
NOTICE:  table "place" does not exist, skipping
NOTICE:  type "keyvalue" does not exist, skipping
NOTICE:  type "wordscore" does not exist, skipping
NOTICE:  type "stringlanguagetype" does not exist, skipping
NOTICE:  type "keyvaluetype" does not exist, skipping
NOTICE:  function get_connected_ways(pg_catalog.int4[]) does not exist,
skipping
Allocating memory for dense node cache
Allocating dense node cache in block sized chunks
Node-cache: cache=768MB, maxblocks=0*98305, allocation method=8192
Mid: pgsql, scale=10000000 cache=768
Setting up table: planet_osm_nodes
NOTICE:  table "planet_osm_nodes" does not exist, skipping
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"planet_osm_nodes_pkey" for table "planet_osm_nodes"
Setting up table: planet_osm_ways
NOTICE:  table "planet_osm_ways" does not exist, skipping
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"planet_osm_ways_pkey" for table "planet_osm_ways"
Setting up table: planet_osm_rels
NOTICE:  table "planet_osm_rels" does not exist, skipping
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"planet_osm_rels_pkey" for table "planet_osm_rels"

Reading in file: /home/myusername/Nominatim/utils/us-northeast.osm.bz2
Processing: Node(26470k 43.8k/s) Way(0k 0.00k/s) Relation(0 0.00/s)WARNING:
Found Out of order node 538228380 (34080045,668) - this will impact the
cache efficiency
Processing: Node(39372k 45.6k/s) Way(2783k 2.00k/s) Relation(22300
446.00/s)  parse time: 2305s

Node stats: total(39372724), max(1910357181) in 863s
Way stats: total(2783089), max(180606791) in 1392s
Relation stats: total(22300), max(2409281) in 51s
node cache: stored: 37092092(94.21%), storage efficiency: 36.85% (dense
blocks: 98304, sparse nodes: 0), hit rate: -1827061.00%
Stopping table: planet_osm_nodes
Stopping table: planet_osm_ways
Stopping table: planet_osm_rels
Stopped table: planet_osm_nodes in 0s
Building index on table: planet_osm_rels (fastupdate=off)
Building index on table: planet_osm_ways (fastupdate=off)
Stopped table: planet_osm_rels in 0s

-----

This is where things start to get very slow, and the CPU/memory usage drops
to near idle levels. Finally it gets stuck at the stage, the entire output
till this stage can be viewed at http://paste.laravel.com/5yB.

----
addgeometrycolumn
--------------------------------------------------------------------------
 public.import_polygon_error.prevgeometry SRID:4326 TYPE:GEOMETRY DIMS:2
(1 row)

                            addgeometrycolumn
-------------------------------------------------------------------------
 public.import_polygon_error.newgeometry SRID:4326 TYPE:GEOMETRY DIMS:2
(1 row)

CREATE INDEX
CREATE TABLE
CREATE INDEX
CREATE SEQUENCE
CREATE TABLE
ALTER TABLE
CREATE INDEX
CREATE TABLE
ALTER TABLE
Partitions




--------
----<-----------------< It gets stuck at this point....>

I checked the newly created database 'nominatim'. There are lots of tables
created, but most of them are empty. Any idea why does it get soooo slow?
Or has it crashed?

Thank you for any suggestions!! :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20120913/50766192/attachment.html>


More information about the dev mailing list