Re: clock_timestamp() and transaction_timestamp() function

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: clock_timestamp() and transaction_timestamp() function
Дата
Msg-id 22661.1070293956@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: clock_timestamp() and transaction_timestamp() function  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-patches
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> This is a nonstarter, as is the previous proposal to have a single
>> function with an explicit parameter that selects the behavior.  The
>> reason is that any such function would have to be treated as completely
>> non-optimizable.

> Why?  We would just need to ensure that the mode cannot be changed at
> critical times.

"critical time" being anywhere within a session, I guess?  Either that
or keep track of whether any cached plans depend on the stability
assumption.

            regards, tom lane

В списке pgsql-patches по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: clock_timestamp() and transaction_timestamp() function
Следующее
От: Manfred Koizar
Дата:
Сообщение: Re: [HACKERS] Index creation takes for ever