Re: Odd transaction timestamp sequence issue - Mailing list pgsql-general

From Jeff Amiel
Subject Re: Odd transaction timestamp sequence issue
Date
Msg-id 4448F802.6000803@istreamimaging.com
Whole thread Raw
In response to Re: Odd transaction timestamp sequence issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Odd transaction timestamp sequence issue  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
it is done using now()....
But what I don't understand is how the transaction that started first
could 'see' the record that hadn't been changed yet by the initial
update to 'COMPLETE'?
I thought:
"Each transaction sees a snapshot (database version) as of its
starttime, no matter what other transactions are doing while it runs"


> How is the "when" column determined?  You did not show it in your SQL
> commands.
>
> If it's being driven off now() or CURRENT_TIMESTAMP, then the above
> isn't all that surprising, because the value is the time of transaction
> start not the time at which the update was made.
>
>

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Odd transaction timestamp sequence issue
Next
From: Vivek Khera
Date:
Subject: Re: Setup for large database