[Tile-serving] [osm2pgsql] large postgres shared_buffers slows down import (#163)

[Paul Norman]

> Or it could just keep the COPY open and feed it data, rather than opening and closing it each time (but I assume it does it that way because it also wants to do queries on the same connection, and you can't interleave them)

For polygons it needs to fetch the way information from the slim tables.

> Or the creation of the polygon table could be committed before it starts getting used for COPY

The C++ rewrite changed some details of what's committed when - I wonder if it does this now.

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