Re: Replication DB scenario - Mailing list pgsql-novice

From Greg Sabino Mullane
Subject Re: Replication DB scenario
Date
Msg-id 72632d0e189c915842ebccd4aa58e646@biglumber.com
Whole thread Raw
In response to Replication DB scenario  (Ricardo Oliveira <ricardojoliveira@gmail.com>)
List pgsql-novice
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Ricardo Oliveira wrote:

> All the databases should "see" changes between them. For example: DB A
> should be updated with changes in DB B and DB C, DB B should be updated
> with changes in DB A and DB C, etc..
...
> - What would be my best choices for data replication between these
> databases? Windows solutions would be preferable but Linux solutions are
> not excluded.

Bucardo can handle this. I'm not aware of anything else that can.

> - What would be your main advice regarding a complex scenario like this?
> What should I be looking for?

A different scenario? :)

If you want replication to continue while one of the databases is down,
that will also add more complexity. You will of course need to arrange
so that updates do not conflict, and/or have some tight business logic
about how to handle conflicts. For more details, email the Bucardo
mailing list at bucardo-general@bucardo.org

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201507170940
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlWpBjsACgkQvJuQZxSWSsivRwCgh57SzL/ibik3T1+2pXxmTgUI
iXsAoLn+eW/OYJ9eEbnfUxX9lWQye3xw
=pI7V
-----END PGP SIGNATURE-----




pgsql-novice by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Temporary table and dump
Next
From: Dan Webb
Date:
Subject: pgloader CSV to table column formatting