[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OSM-dev] [Maposmatic-dev] Re: Growth of on-disk size of OSM databas
From: |
Frederik Ramm |
Subject: |
Re: [OSM-dev] [Maposmatic-dev] Re: Growth of on-disk size of OSM database |
Date: |
Wed, 14 Jul 2010 17:08:44 +0200 |
User-agent: |
Thunderbird 2.0.0.24 (X11/20100317) |
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 address@hidden ## N49°00'09" E008°23'33"