On Friday 09 February 2007, Jan Wieck wrote:
> I am not sure, I would have to look at what exactly that hook provides.
> The key to a Lamport timestamp is that it is advancing it commit order
> (plus some other things ... of course). If the hook can guarantee that
> the calls are made always in commit order, serialized without any race
> condition possible, it would probably be suitable.
Actually what we do is a bit stronger. We use the commit hook to enforce an
externally defined commit order. In our case, this is defined by a group
communication protocol, which is even allowed to reorder a pair of
transactions originating from the same replica. Therefore, achieving a commit
order that is consistent with a local clock should be straightforward.
Regards,
--
Jose Orlando Pereira
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
