[Bucardo-general] Txntime should be commit time

Gustavo Tonini gustavotonini at gmail.com
Mon Aug 29 01:38:23 UTC 2016

Hey guys,
I have an environment where the current implementation of txntime (set to
transaction start time) is causing problems. It has long transactions so
the conflict resolution strategy (latest) sometimes overwrites the real
latest value (which belongs to the most recently committed transaction but
which has unfortunatelly started a long time ago).

Supposing an accurate clock in all servers, a txntime set to transaction
commit time should solve this issue.

Do you see any workaround or another strategy to avoid this problem?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20160828/59c922a9/attachment.html>

More information about the Bucardo-general mailing list