Re: clock_timestamp() and transaction_timestamp() function - Mailing list pgsql-patches

From Tom Lane
Subject Re: clock_timestamp() and transaction_timestamp() function
Date
Msg-id 22661.1070293956@sss.pgh.pa.us
Whole thread Raw
In response to Re: clock_timestamp() and transaction_timestamp() function  (Peter Eisentraut <peter_e@gmx.net>)
List 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 by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: clock_timestamp() and transaction_timestamp() function
Next
From: Manfred Koizar
Date:
Subject: Re: [HACKERS] Index creation takes for ever