From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Vilson farias <vilson(dot)farias(at)digitro(dot)com(dot)br> |
Cc: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Some timestamp problems |
Date: | 2002-08-29 22:55:27 |
Message-ID: | 20020829225527.GA347@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Aug 29, 2002 at 17:59:15 -0300,
Vilson farias <vilson(dot)farias(at)digitro(dot)com(dot)br> wrote:
> But there are two kind of problems there. First related with big date
> values. ok, bot big deal yet :), but the second is taking my attention : if
> you put a time with 995 to 999 miliseconds, it's represented as 60seconds
> instead of 59seconds and 995 to 999 miliseconds. I don't think it's alright,
> because I've never seen a datetime with 60seconds value (60 seconds is
> always the next minute, in my conception). I would like some light here, is
> it just a psql problem to show datetime values or a internal datetime
> storage problem?
Note that if you are using UTC there are leap seconds stuck in or removed
from time to time. So you can have a 61st (and I think even a 62nd) second
in a given minute.
From | Date | Subject | |
---|---|---|---|
Next Message | =?ISO-8859-1?Q?Gr=E9gory_Faruch?= | 2002-08-29 23:30:30 | configure script problem |
Previous Message | Tim Ellis | 2002-08-29 22:36:26 | Re: Silencing NOTICEs in Perl Pg |