[Tile-serving] [osm2pgsql] Hang on unsimplified diffs (#112)

[jeffjanes]

You are correct, the bug I pointed to would make the client (psql in that case, osm2pgsql in your case) consume 100%, not the PostgreSQL backend do so, so this must be a different bug.  But it seems like it must be a bug in PostgreSQL, not in osm2pgsql, to cause this.  

You could try submitting a bug report, but unfortunately I doubt many PostgreSQL hackers have the hardware, bandwidth, skills, or patience to reproduce bugs that require a full planet import and then diffs.  I know I don't.

Can you do a strace on the process which is consuming the CPU, "strace -p <PID>", and get a few hundred lines to see what is going on? And better yet a stack trace ("gdb -p <PID>", then "bt" at the debugger prompt)?

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/112#issuecomment-31203734
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20131225/2ec5f6a5/attachment.html>