Hi Jon,
Thank you for your work.
We have SVN Revision no. r24100 of osm2pgsql installed.
While still trying to resolve an out-of-memory issue with osm2pgsql in
slim-mode we realized that the error output goes to the usual log
output.
It would be very helpful to print the error to it's separate
On Sun, 2011-06-05 at 01:23 +0200, Stefan Keller wrote:
Hi Jon,
Thank you for your work.
We have SVN Revision no. r24100 of osm2pgsql installed.
While still trying to resolve an out-of-memory issue with osm2pgsql in
slim-mode we realized that the error output goes to the usual log
output.
Hi,
We recently upgraded to PostgreSQL 9 and PostGIS 1.5.2 and hence were
forced to rebuild osm2pgsql because of new versions of its
dependencies (e.g., libgeos).
Afterwards, we tried to insert Switzerland data with the following command:
$ osm2pgsql --create --database gisdb --prefix osm
On Fri, 2011-05-06 at 20:23 +0200, Stefan Keller wrote:
Hi,
We recently upgraded to PostgreSQL 9 and PostGIS 1.5.2 and hence were
forced to rebuild osm2pgsql because of new versions of its
dependencies (e.g., libgeos).
Afterwards, we tried to insert Switzerland data with the following
Stefan Keller sfkel...@gmail.com wrote:
Unfortunately, only the osm_point table was filled with data,
osm_polygon and osm_line were empty. This was not the case before the
upgrade of the mentioned components.
Hm looks like I broke something :(
I did not try --hstore-all anymore after adding
Sven Geggus li...@fuchsschwanzdomain.de wrote:
Hm looks like I broke something :(
Puh, fortunately it looks like I did not :)
planet_osm_polygon and planet_osm_line are fine in either case here:
--hstore, --hstore-all and no hstore.
Just 4TR:
I'm running a custom backport of postresql 9.0
6 matches
Mail list logo
