Hi, Le mercredi 16 avril 2008, Rob Collins a écrit : > There is one central server with 19 branches. Some tables need to replicate > from the central server to the branches. Other tables are centralised from > the branches into one totalling table at the centre. A few tables need to > replicate in both directions. I'm working on some projects here with this very need (and same scale), and I plan to use londiste (master/slaves asynchronous solution) replication solution, which I already use in production on some other project. The fact is that we want the "branches" to still be fully available in case of network or central server failure, so we don't buy into synchronous replication; which is not available yet into PostgreSQL as far as I know, even if one of the basics building-block alternatives is provided into -core, namely Two Phase Commit. http://www.postgresql.org/docs/8.3/static/sql-prepare-transaction.html You'll find londiste documentation at both following places, the latter is up-to-date with last 2.1.6 release, the former I'm not sure about it. http://skytools.projects.postgresql.org/doc/ http://pgsql.tapoueh.org/skytools/ Hope this helps, regards, -- dim
Attachment:
signature.asc
Description: This is a digitally signed message part.