Re: BUG #1927: incorrect timestamp returned

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: postgres(at)saparev(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1927: incorrect timestamp returned
Date: 2005-10-04 14:40:11
Message-ID: 200510041440.j94EeBN08952@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

Kouber Saparev wrote:
> >>
> >>select timestamp '2005-09-23 23:59:59.9999999'
> >>
> >>I get the following result (note the value of the seconds):
> >>
> >>2005-09-23 23:59:60.00
> >
> >
> > It's the leap second.
> >
> >
>
> It is not a leap second. Leap seconds are always either on the 30th of
> June or on the 31th of December.
>
> Here there is a list of all the leap seconds so far:
> http://en.wikipedia.org/wiki/Leap_second
>
> And, in fact, the wrong result is the same for each date, regardless of
> the year, month or day.

Right. We allow leap seconds for any date/time. Are you saying we
should only allow them for certain dates/times?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2005-10-04 15:00:16 Re: BUG #1937: Parts of information_schema only accessible to owner
Previous Message Tom Lane 2005-10-04 14:25:33 Re: PostgreSQL Database export from Linux to Windows

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2005-10-04 15:20:15 Re: BUG #1927: incorrect timestamp returned
Previous Message Sokolov Yura 2005-10-04 08:24:30 Patch for PLPYTHONU - adding TD["relname"]