[Bucardo-general] Sequence of events.

[Greg Sabino Mullane]

> Obviously I do not understand something in the replicatuion process.
> Could anybody please explain me  where replication data had been stored?

It's not exactly clear from your email what happened. I can give you a
high-level overview of what is supposed to happen however. The INSERTs will
cause rows to be added to the bucardo_delta table, which will show up once the
END TRANSACTION is reached. If the table is configured that way, it will also
kick off a sync. You can check for a trigger name starting with
'bucardo_triggerkick' on the table. Bucardo will then query the bucardo_delta
rows on the source and the target, figure out which rows need to go where, and
make the changes. In this case, it should do a lot of inserts to the other
database. Keep in mind the bucardo_delta only stores the primary keys: the
actual data for the rest of the columns is stored in the original table.

If you are having problems, it might be best to break the problem down into
smaller chunks (such as a single INSERT block) and then try to follow along in
the Bucardo logs. They are very verbose but should be understandable. If not,
let us know which parts are not making sense.


-- 
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: 226 bytes
Desc: OpenPGP digital signature
Url : https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20090310/622f1580/attachment.bin