Re: BUG #1927: incorrect timestamp returned - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #1927: incorrect timestamp returned
Date
Msg-id 200510041440.j94EeBN08952@candle.pha.pa.us
Whole thread Raw
In response to Re: BUG #1927: incorrect timestamp returned  (Kouber Saparev <postgres@saparev.com>)
Responses Re: BUG #1927: incorrect timestamp returned
Re: BUG #1927: incorrect timestamp returned
List pgsql-bugs
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@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: BUG #1937: Parts of information_schema only accessible
Next
From: Peter Eisentraut
Date:
Subject: Re: BUG #1937: Parts of information_schema only accessible to owner