Simon Riggs <simon@2ndQuadrant.com> wrote:
> 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).
Sure, that's why I want it.
> 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.
Only if you assume that multi-master means identical databases all
replicating the same data to all the others. If I have 72 master
replicating non-conflicting data to one consolidated database, I
consider that to be multi-master, too. Especially if I have other
types of databases replicating disjoint data to the same
consolidated database, and the 72 sources have several databases
replicating disjoint sets of data to them. We have about 1000
replications paths, none of which create a loop which can send data
back to the originator or cause conflicts.
Of course, none of these databases have the same OID for any given
object, and there are numerous different schemas among the
replicating databases, so I need to get to table and column names
before the data is of any use to me.
-Kevin
