On Wed, Oct 31, 2012 at 12:11:44PM -0700, David E. Wheeler wrote: > Fellow Bucardoans, > > At a quick glance, I see no support for two-phase commit > in the 5.0 code base.
Correct. Big gotcha is 2PC does not work with LISTEN/NOTIFY. ... > So good that it commits the databases written to, first. But what > happens if there are three being written to, the first two commit, > but the last one fails? Shouldn't the first two really be rolled > back, then? Two-phase commit on databases that support it would allow that. The track will not be updated, so the next time Bucardo runs it will get all databases in sync again. It's debatable if we really want the behavior that one down db blocks all the rest, given our highly async nature. -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8
pgpv3THydKctt.pgp
Description: PGP signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
