Re: Odd transaction timestamp sequence issue

Поиск
Список
Период
Сортировка
Искать
От
Jeff Amiel
Тема
Re: Odd transaction timestamp sequence issue
Дата
Msg-id
4448F802.6000803@istreamimaging.com
Ответ на
Список
Дерево обсуждения
Odd transaction timestamp sequence issue Jeff Amiel <jamiel@istreamimaging.com>
Re: Odd transaction timestamp sequence issue Martijn van Oosterhout <kleptog@svana.org>
Re: Odd transaction timestamp sequence issue Tom Lane <tgl@sss.pgh.pa.us>
Re: Odd transaction timestamp sequence issue Jeff Amiel <jamiel@istreamimaging.com>
Re: Odd transaction timestamp sequence issue Tom Lane <tgl@sss.pgh.pa.us>
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 по дате отправления
От: Martijn van Oosterhout
Дата:
От: Vivek Khera
Дата:
Сообщение: Re: Setup for large database
FAQ