The sibling comment is correct: the FAQ is out of date. Bucardo 4 supported only 2 masters; B5 is N >= 2. I'll try briefly to answer your questions, having use

The sibling comment is correct: the FAQ is out of date. Bucardo 4 supported only 2 masters; B5 is N >= 2. I'll try briefly to answer your questions, having used Bucardo for several years, having a (woefully under-utilized) commit bit, and being a somewhat active participant on the mailing list and in #bucardo. Conflicts are handled in one of a number of user-selectable ways ("latest" wins, "source" wins, &c). They're selectable on a per-table basis. If the configuration DB were to stop, I don't actually know what would happen. I've never faced that scenario. AIUI, however, Bucardo only reads its configuration on startup, so it shouldn't break anything unless you were to try to change your replication configs (or restart, which doesn't typically need to happen), at which point you'd be able to address it. If syncing stops, "deltas" (which are merely a timestamp and the pkey of the changed record) accumulate in their source databases until syncing is resumed. Healing consists of those deltas being replayed against their targets, as managed by the selected conflict resolution strategy.