[osmosis-dev] read-change-interval stuck

[Peter Körner]

Am 14.08.2010 00:12, schrieb Frederik Ramm:
> Yes. That way I can always be sure not to start loading something into
> the DB before it has fully downloaded. Probably paranoia on my part,
> since transactions should make sure everything is right, but ...

I'm doing it the same way but for another reason:
once the import has finished, I'll free the lock and thus open the way 
for new diffs to be loaded, keeping the lag low. After releasing the 
lock, I start with expire.py to expire tiles. That way expire.py can run 
while osm2pgsql is importing a new chunk of data in parallel.

Peter