From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Wang Mike <itlist(at)msn(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: clock_timestamp() and transaction_timestamp() function |
Date: | 2003-12-01 15:53:32 |
Message-ID: | 200312011553.hB1FrWv18540@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)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.
Ewe, that isn't going to work --- making the value unchangable during the
session.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2003-12-01 18:17:10 | Re: [HACKERS] Index creation takes for ever |
Previous Message | Bruce Momjian | 2003-12-01 15:52:46 | Re: clock_timestamp() and transaction_timestamp() function |