Hello, I have a question regarding log-shipping replication, but let me first explain what I currently do. Usually Openstreetmap Tile Servers are currently set up using a PostgreSQL/Postgis Database which stores the data need for rendering raster map-tiles. After the initial import of a complete OSM dataset it is possible to replicate changes to this database using cyclic calls to openstreetmaps own tool called osm2pgsql. Unfortunately there is one major drawback with this approach: 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)! So here is my question: Would it be possible to have a setup, where one master data database will act in the above matter (still running osm2pgsl) but will also provide publicly availabe data for log-shipping standby servers? We would need to be able to explicitely specify the tables to be replicated or the other way round explicitely exclude a couple of them. If this helps it would be possible to separate them by tablespaces. Regards Sven -- # Turn on/off security. Off is currently the default (found in MongoDB default configfile) /me is giggls@ircnet, http://sven.gegg.us/ on the Web -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
