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

From Stephen Frost
Subject Re: Proposal: Commit timestamp
Date
Msg-id 20070126143849.GP24675@kenobi.snowman.net
Whole thread Raw
In response to Re: Proposal: Commit timestamp  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: Proposal: Commit timestamp  (Andrew Dunstan <andrew@dunslane.net>)
Re: Proposal: Commit timestamp  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
* Jan Wieck (JanWieck@Yahoo.com) wrote:
> On 1/26/2007 2:37 AM, Naz Gassiep wrote:
> >I would be *very* concerned that system time is not a guaranteed
> >monotonic entity. Surely a counter or other internally managed mechanism
> >would be a better solution.
>
> Such a counter has only "local" relevance. How do you plan to compare
> the two separate counters on different machines to tell which
> transaction happened last?

I'd also suggest you look into Lamport timestamps...  Trusting the
system clock just isn't practical, even with NTP.  I've developed
(albeit relatively small) systems using Lamport timestamps and would be
happy to talk about it offlist.  I've probably got some code I could
share as well.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Proposal: Snapshot cloning
Next
From: Tom Lane
Date:
Subject: Re: crash on 8.2 and cvshead - failed to add item to the