[OSM-talk] Bug in using osm2pgsql to keep up with dailies

[Michal Migurski]

>> So I'm definitely doing the bbox thing - I ran out of space on the
>> volume when doing a slim import of planet.osm with a box that covered
>> only the extended SF Bay Area. Seems like that should be fairly
>> reasonable, right?
>
> Perhaps the slim mode is not taking the bounding box into account.
> I'll take a look.

Any news?


>> Probably the right thing to do would be to get the import done once
>> with a larger volume available to Postgres (EC2 does give you a
>> secondary disk at /mnt that's over 100GB), then keep up with
>> incrementals moving forward after the initial inconvenience.
>
> 100GB would definitely be enough. I've seen the full slim-mode planet
> import taking around 40GB. This code to handle the diff mode import is
> all very new and does not scale up to handling the whole planet yet.


So I'm running in further frustrations here.

Slim mode over the full planet won't work without the intarray module,  
but it's not included in contrib/ for postgresql-8.3 on Debian Lenny.  
Where should I be looking for this?

-mike.

----------------------------------------------------------------
michal migurski- mike at stamen.com
                  415.558.1610