On Thu, Mar 26, 2015 at 04:32:00PM +0100, Sven Geggus wrote:
>
> We need to somehow save the state of the osm database to be able to apply
> future changes. This is currently done using a few tables in the target
> database. However these tables are not needed for map rendering and are
> consuming by far the most disk space (still somewhat expensive on SSD)!
This doesn't actually solve your problem, but you could mitigate the
cost by putting those tables on spinning-rust disks using tablespaces
or symlinks or whatever.
Best regards,
A
--
Andrew Sullivan
ajs@crankycanuck.ca