Re: Proposal: Commit timestamp - Mailing list pgsql-hackers

From Neil Conway
Subject Re: Proposal: Commit timestamp
Date
Msg-id 1169768859.5432.9.camel@localhost.localdomain
Whole thread Raw
In response to Proposal: Commit timestamp  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: Proposal: Commit timestamp
List pgsql-hackers
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,
etc.)

> Comments, changes, additions?

Would this feature have any use beyond the specific project/algorithm
you have in mind?

-Neil




pgsql-hackers by date:

Previous
From: Jeremy Drake
Date:
Subject: Re: [pgsql-patches] unprivileged pl install
Next
From: Tom Lane
Date:
Subject: Re: Proposal: Commit timestamp