| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: time stops within transaction |
| Date: | 2000-10-18 03:21:07 |
| Message-ID: | 200010180321.XAA26807@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Wow, that is strange.
> I just ran into a strangest thing: within transaction, select now() will
> always return time when transaction started. Same happens with select
> 'now'::timestamp.
>
> This is with 7.0. I have not tested it with CVS.
>
> I am not sure what causes this. I assume that result of now() is cached by
> fmgr. Is there a way to declare functions 'not-cacheable-ever'? If there
> is, such should be applied to now().
>
> -alex
>
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-18 03:33:54 | Re: time stops within transaction |
| Previous Message | Alex Pilosov | 2000-10-18 02:40:33 | time stops/workaround |