On 20 June 2012 04:31, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
> I've done a lot of MM replication,
> and so far have not had to use a topology which allowed loops.
The proposal is to use WAL to generate the logical change stream. That
has been shown in testing to be around x4 faster than having a
separate change stream, which must also be WAL logged (as Jan noted).
If we use WAL in this way, multi-master implies that the data will
*always* be in a loop. So in any configuration we must be able to tell
difference between changes made by one node and another.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
