On Thu, 2007-01-25 at 18:16 -0500, Jan Wieck wrote:
> For conflict resolution purposes in an asynchronous multimaster system,
> the "last update" definition often comes into play. For this to work,
> the system must provide a monotonically increasing timestamp taken at
> the commit of a transaction.
Do you really need an actual timestamptz derived from the system clock,
or would a monotonically increasing 64-bit counter be sufficient? (The
assumption that the system clock is monotonically increasing seems
pretty fragile, in the presence of manual system clock changes, ntpd,
> Comments, changes, additions?
Would this feature have any use beyond the specific project/algorithm
you have in mind?
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2007-01-25 23:49:43|
|Subject: Re: Proposal: Commit timestamp |
|Previous:||From: Jeremy Drake||Date: 2007-01-25 23:38:31|
|Subject: Re: [pgsql-patches] unprivileged pl install|