On 1/22/2013 8:45 PM, Greg Sabino Mullane wrote:
Deltas are not tracked per target, but commit timestamps are (aka bucardo_track). In other words, Bucardo can be taught the list of target for each table, and will thus never purge a bucardo_delta record until it has been replicated to all systems. This is already in place and could work out for you. One drawback is that deltas can never be completely cleaned until everyone has come back to life and copied the row. So a long-dead system could eventually bloat up the bucardo_delta table. As B5 uses multiple, per-table bucardo_delta tables, this is not much of an issue anymore.
Thanks Greg. Would the appropriate approach to implement this be to set up each mobile database with it's own set of uniquely named syncs that just includes itself and the central database? Can each single table on the central database participate in multiple syncs without problem? Do you think there would be much of a performance impact on the central server if each table ended up with a few hundred extra bucardo_kick_% triggers?
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
