> My server is a dual quad core with 16GB of RAM and 10GB of swap space and > decent disks, yet the import of just Denmark (~60MB compressed) takes several > hours and eventually crashes with the below message and all RAM and swap in > use. The crash appears to occur on " insert into placex select * from place > where osm_type = 'N';" in gazetteer-index.sql.
That is far too slow - I'd expect 2 hours start to finish (just a random guess). Worth noting that unfortunately your quad core doesn't do you that much good because postgresql can only utilise one processor per query :( > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and repeat > your command. > CONTEXT: PL/pgSQL function "add_location" line 24 at IF > PL/pgSQL function "placex_insert" line 200 at assignment > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > connection to server was lost I've never seen anything like this while I've been developing. The nearest I've seen is a seg fault while processing invalid geometry - but that just doesn't happen for nodes! I'd suggest you uncomment the 'RAISE WARNING '%',NEW.osm_id;' line at the top of placex_insert in gazetteer-functions.sql so you can follow the progress of the insert. You could also try uncomment the RETURN NEW; just before the line 'The following is not needed until doing diff updates, and slows the main index process down' to see if that has an effect. -- Brian _______________________________________________ Geocoding mailing list [email protected] http://lists.openstreetmap.org/listinfo/geocoding
