Re: time stamp

Tom Lane wrote:

>Felipe Nascimento <Felipe(dot)Nascimento(at)multivalor(dot)com(dot)br> writes:
>
>
>>let's imagine that my server resides in Time Zone(TZ) "-00", and one user
>>resides in TZ "-05". Let=B4s say that 12p.m. to the user is 3p.m. to the
>>server, on the same day.
>>
>>
>
>
>
>>Let's say that the user inputs a date for a business meeting: "2002-06-20
>>12:00:00". The server will save "2002-06-20 12:00:00-00"??
>>
>>
>
>No, it won't. If the user has TimeZone set to -05, as he should, then
>his input of '2002-06-20 12:00:00' will be read as '2002-06-20 12:00:00-05'.
>And it will be displayed to him that way. But if someone else who
>has TimeZone set differently looks at the stored value, it will be shown
>to them properly converted into their timezone.
>
This can be a problem if the client is a web application in a fixed
timezone and the person viewing the results is in a different time zone.

>
>This all works exactly the same as ordinary Unix timekeeping --- in
>essence, everything is GMT inside the system, and rotation into a
>particular timezone happens on-the-fly when a timestamp value is
>entered or displayed. The TimeZone variable corresponds to the TZ
>environment variable of Unix.
>
Another option is to get the timestamp via conversion to abstime to
integer and your script or application format that timestamp (integer)
to local format (string).
mytime::abstime::integer (this should be a GMT timestamp [int] if I
remember correctly).

Someone correct me if I'm wrong.

>
>
>
>>My question is: how to manage this so I can send the email to the user at
>>his 11 o'clock (8 a.m. server time)???=20
>>
>>
>
>If you let the system do what it wants to do, it will do the right
>thing.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://archives.postgresql.org
>
>