From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | "Christopher J(dot) Bottaro" <cjbottaro(at)alumni(dot)cs(dot)utexas(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: CURRENT_TIMESTAMP vs actual time |
Date: | 2005-04-21 14:42:10 |
Message-ID: | 20050421144210.GB16183@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 21, 2005 at 09:22:26AM -0500, Christopher J. Bottaro wrote:
> John DeSoi wrote:
>
> >
> > On Apr 20, 2005, at 6:15 PM, Christopher J. Bottaro wrote:
> >
> >> I understand that CURRENT_TIMESTAMP marks the beginning of the current
> >> transaction. I want it to be the actual time. How do I do this?
> >> timeofday() returns a string, how do I convert that into a TIMESTAMP?
> >
> > timeofday()::timestamp;
>
> Great, that did it, thanks. I also found out that you can say
> CAST(timeofday() AS TIMESTAMP). I assume its the same thing...
Not sure it's the same thing. IIRC, CURRENT_TIMESTAMP returns a
timestamp with time zone, whereas casting to timestamp unadorned returns
a timestamp without time zone. Try
cast(timeofday() as timestamptz)
or
cast(timeofday() as timestamp with time zone)
It may not matter a lot but you may as well be aware of the difference ...
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"En las profundidades de nuestro inconsciente hay una obsesiva necesidad
de un universo lógico y coherente. Pero el universo real se halla siempre
un paso más allá de la lógica" (Irulan)
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-04-21 14:42:54 | Re: Suggestions |
Previous Message | Christopher J. Bottaro | 2005-04-21 14:22:26 | Re: CURRENT_TIMESTAMP vs actual time |