I think we have made some progress on updating the software stack (The
re-import will occur into a postgresql 9.1 database with the latest
osm2pgsql) and are nearly ready to start the import.
In order to have enough space on disk for the new import, the following
db tables will be dropped: "planet_line_old, planet_point_old,
planet_polygon_old and planet_roads_old" These are presumably old tables
that were left over from the previous import and aren't used anymore.
Furthermore, the tables "planet_nodes, planet_ways and planet_rels" will
be dropped, as those are only used for updating which is currently not
The rendering tables will likely be kept during the import and should
continue to be usable, both for rendering and other purposes. Once the
import into the new db is complete and up-to-date again, the dbs will be
switched and the old one deleted.
Tirex for now has, however, been set to only render missing tiles to
minimize the load on the database during the re-import.
The import is intended to occur with the default set of db columns
together with the hstore extensions.
Once everything is up-to-date again, I will try and enable tile expiry
at least for the 5 - 10 most used styles, but we will see how that goes.
On 11/18/2011 07:38 AM, Kay Drangmeister wrote:
Am 18.11.2011, 08:57 Uhr, schrieb Kai Krueger <kakrueger(a)gmail.com>om>:
[osm_mapnik database is not being updated anymore
since a while]
To try and minimize disruption, I would like to
ask who, or which tools,
are currently using the osm_mapnik database? Is the downtime going to be
an issue for anyone?
I consider the downtime lasting already for two months now, so some
additional days are not worth mentioning. :o)
Maps-l mailing list