[Bucardo-general] recovering from failed swap sync

[Greg Sabino Mullane]

> How can I determine why Bucardo thinks there's a conflict and, 
> more importantly, resolve the conflict without issue?

The bucardo logs should be telling you the offending row. You could try 
and find it manually by looking at the bucardo_delta table and grabbing 
all the pkeys for the offending table. Do this on both sides and compare 
the numbers to find the overlap.

> The row that's causing the conflict existed only on the source side. 
> The remote side did not have this row.  In an attempt to resolve this, 
> I manually inserted the row on the target side.

If I am understanding this correctly, you probably need to remove the 
bucardo_delta record manually, probably from the target side. As well 
as remove that manually inserted row. At the end of the day, only one 
server should mention that pkey, both at the bucardo_delta level and 
in the table itself.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Digital signature
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20130827/6c1d1a8e/attachment.sig>