Hello, I am already using the -s (slim) parameter. See top of this image:

http://www.prodevelop.es/files/fm/public/downloads/wxp_console.png

Regards,
Juan Lucas


--- On Mon, 7/19/10, Emilie Laffray <[email protected]> wrote:

From: Emilie Laffray <[email protected]>
Subject: Re: [OSM-dev] OSM-to-PostGIS issues
To: "Juan Lucas Domínguez Rubio" <[email protected]>
Cc: [email protected]
Date: Monday, July 19, 2010, 1:58 PM



On 19 July 2010 12:54, Juan Lucas Domínguez Rubio <[email protected]> 
wrote:

Hello, list:
 
I've tried to export a 9.5 GB (150 GB uncomp.) planet to a PostGIS DB @ 
localhost on a Windows XP machine (1.5 GB RAM). I have tuned the DB parameters 
like this:

 
shared_buffers = 256MB
checkpoint_segments = 20
maintenance_work_mem = 256MB
autovacuum = off

postgresql.conf file here:

http://www.prodevelop.es/files/fm/public/downloads/postgresql.conf.txt


but I still get the same error message I got in the previous attempt (with no 
DB tuning). See command parameters and error message here:

http://www.prodevelop.es/files/fm/public/downloads/wxp_console.png



Any ideas why this happens?
Not enough RAM?
osm2pgsql is
 not Windows-friendly?
DB tuning needs double-checking?
Anybody has done this on WXP? 

Not enough ram. You should try running osm2pgsql with the slim option. It uses 
much less ram but uses more disk space.


Emilie Laffray




      
_______________________________________________
dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/dev

Reply via email to