On Sun, Jun 30, 2013 at 11:24 PM, Mike Dewhirst <mi...@dewhirst.com.au> wrote: > mulianto and Avraham > > Thanks for your suggestions. Dumping data isn't the entire problem - which > is this: > > There will be an *ongoing* need to add new data from tables in one database > to the same-named tables in another database on a remote machine. Two of the > tables are in a m2m relationship. >
Sounds like you want replication from one database to another. Recent versions of Postgres have built in support for what they call "log shipping" or "streaming replication", where logs of updates are transferred to backup servers and executed: http://www.postgresql.org/docs/current/static/warm-standby.html This requires some manual setup of your servers to transfer the logs. There are other forms of replication, postgresql actually provide a useful table listing the various solutions, their pros/cons, and links on how to implement them. Lots of the solutions are not part of postgresql itself, but use third party packages like slony to effect the replication. See here: http://www.postgresql.org/docs/current/static/different-replication-solutions.html Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
