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? Gustavo.
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
