From: | Kouber Saparev <postgres(at)saparev(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1927: incorrect timestamp returned |
Date: | 2005-10-03 18:28:37 |
Message-ID: | 43417855.1090604@saparev.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-patches |
>>
>>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.
--
Kouber Saparev
http://kouber.saparev.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Alon Goldshuv | 2005-10-03 21:53:44 | BUG #1936: Read-only transactions ignored in COPY |
Previous Message | Jean-Pierre Pelletier | 2005-10-03 16:21:09 | Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2 |
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2005-10-03 19:21:21 | Re: [HACKERS] External Sort timing debug statements |
Previous Message | Qingqing Zhou | 2005-10-03 16:28:26 | Re: cleanup log_disconnections() |