txid and current_timestamp

Started by Vlad Arkhipovalmost 14 years ago3 messagesgeneral
Jump to latest
#1Vlad Arkhipov
arhipov@dc.baikal.ru

Is it guaranteed that if txid2 > txid1 then current_timestamp in
transaction 2 >= current_timestamp in transaction 1?

#2Jasen Betts
jasen@xnet.co.nz
In reply to: Vlad Arkhipov (#1)
Re: txid and current_timestamp

On 2012-06-26, Vlad Arkhipov <arhipov@dc.baikal.ru> wrote:

Is it guaranteed that if txid2 > txid1 then current_timestamp in
transaction 2 >= current_timestamp in transaction 1?

no.

--
⚂⚃ 100% natural

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Jasen Betts (#2)
Re: txid and current_timestamp

Jasen Betts <jasen@xnet.co.nz> writes:

On 2012-06-26, Vlad Arkhipov <arhipov@dc.baikal.ru> wrote:

Is it guaranteed that if txid2 > txid1 then current_timestamp in
transaction 2 >= current_timestamp in transaction 1?

no.

To enlarge on that: current_timestamp is set at the moment of receipt
from the client of a transaction's first command. XID is not set until
(and unless) the transaction does something that modifies the database.
The elapsed time between can be quite variable depending on what
commands the client issues.

Even if this weren't the case, I wouldn't recommend relying on such an
assumption, because of factors like clock skew between different
processors.

regards, tom lane