On 08/15/2011 12:58 PM, Peter Körner wrote:
Hi
Am 12.08.2011 17:37, schrieb Kai Krueger:
r25070: Make use of prepared geometries from geos-3.1+. These dramatically speed up the polygon tests used by the advanced multipolygon handling code.
r26292: Implement pgsql_nodes_get_list to speed up way and relation processing
we're now running r26543 (intarray branch), let's see if it is faster.
Unfortunately, the first batch didn't look to promising that it was any faster. :-( The majority of the time is still spent in processing relations it seems, with a single relation taking multiple seconds to process. I will try and see if I can at some point figure out what stage of processing relations takes so long, although that would presumably require to rebuild osm2pgsql with some extra instrumentation.
The second batch just crashed some 4 hours into processing and has restarted, so that won't make it any faster either...
Going over pending ways 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. pending_ways failed: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. (7) Error occurred, cleaning up
Somehow the postgresql server crashed.
Earlier, when connecting directly to the database and trying to run some test queries, I noticed that I got some odd error messages. I can't remember the exact wording, but it was something along the line that it failed to write a temporary transaction log file. I am not sure how reproducible that error is, or if it is connected to the crash in osm2pgsql, but it may give some hints.
Kai
Peter
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l