Re: [HACKERS] bug in timestamp and out of range values

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] bug in timestamp and out of range values
Date: 2006-11-03 04:34:14
Message-ID: 454AC6C6.9040205@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

>
> postgres=# select '4714-01-27 BC'::date;
> ERROR: date out of range: "4714-01-27 BC"
> postgres=# select cast(test as date) from timetest;
> test
> ---------------
> 4714-01-27 BC
> (1 row)
>
> postgres=#
> postgres=# select cast('4714-01-27 BC' as date);
> ERROR: date out of range: "4714-01-27 BC"
> postgres=#
>
> This seems pretty broken.
>
> Joshua D. Drake

And further this with timestamp instead of date:

postgres=# create table timestamptest(test timestamp);
CREATE TABLE
postgres=# insert into timestamptest
values (to_date('4714-01-27 BC', 'YYYY-MM-DD BC'));
INSERT 159911988 1
postgres=# select * from timestamptest;
ERROR: timestamp out of range

Sincerely,

Joshua D. Drake

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-11-03 06:18:10 Re: bug in timestamp and out of range values
Previous Message Joshua D. Drake 2006-11-03 04:27:46 Re: [HACKERS] bug in timestamp and out of range values

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-11-03 06:18:10 Re: bug in timestamp and out of range values
Previous Message Joachim Wieland 2006-11-03 04:30:16 "recovering prepared transaction" after server restart message