BUG #7942: Timestamp "19991231 240000" should not be out of range

From: georg(dot)kindermann(at)gmx(dot)at
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #7942: Timestamp "19991231 240000" should not be out of range
Date: 2013-03-14 08:47:42
Message-ID: E1UG3p8-00014S-4D@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 7942
Logged by: Georg Kindermann
Email address: georg(dot)kindermann(at)gmx(dot)at
PostgreSQL version: 9.1.8
Operating system: Debian Wheezy
Description:

select cast('19991231 240000' as timestamp);
--Produces >ERROR: timestamp out of range<

select cast('20000101 000000' as timestamp);
--Works

--For other years both styles work e.g
select cast('19981231 240000' as timestamp);
select cast('19990101 000000' as timestamp);

--1999 to 2000 is no Leap second. Is there something other special? Thanks!

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Josh Kupershmidt 2013-03-14 15:13:02 Re: BUG #7940: Auto increment issue
Previous Message krishnakumar.eeee 2013-03-13 11:01:38 BUG #7940: Auto increment issue