[OSM-dev] [Maposmatic-dev] Re: Growth of on-disk size of OSM database

Frederik Ramm frederik at remote.org
Wed Jul 14 16:08:44 BST 2010


Hi,

Ævar Arnfjörð Bjarmason wrote:
> This is why PostgreSQL administrators usually put VACUUM FULL; in
> their cron.daily, but that doesn't help you at this point.

Actually that never helps; a VACUUM FULL on a full planet slim import on 
a machine with standard disks and memory is very likely to lock the 
database for more than one day even if done regularly.

> Or you could use MySQL instead of PostgreSQL (if that even works
> anymore). It doesn't use the same model for deletion as PostgreSQL, so
> you'll reclaim your space without expensive VACUUM operations.

To my knowledge, osm2pgsql has never supported MySQL.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"




More information about the dev mailing list