From: | "John Huttley" <John(at)mwk(dot)co(dot)nz> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: time stops within transaction |
Date: | 2000-10-18 03:48:43 |
Message-ID: | 005e01c038b6$50531780$1401a8c0@MWK.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
----- Original Message -----
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>
Sent: Wednesday, 18 October 2000 16:21
Subject: Re: [HACKERS] time stops within transaction
> 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.
> >
Actually, thats useful since you can put now() into multiple fields in one
transaction.
The alternative is that CURRENT_TIMESTAMP (??? is that the one) which isn't a
function
and stuffs up when trying to use it as a field default or as part of an
expression in a view.
(Comment true for 6.5.3 at least)
Documentation on time constants and how to misuse them is weak...
Regards
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-10-18 04:01:16 | Re: time stops within transaction |
Previous Message | Tom Lane | 2000-10-18 03:33:54 | Re: time stops within transaction |