From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Do Not Spam <nospam(at)nospam(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Time bug fixed? |
Date: | 2002-07-05 17:24:36 |
Message-ID: | 200207051724.g65HOa822726@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Do Not Spam wrote:
> There has been quite a few mails on the misoperation in date values before the epoc on RH7.3 and pgsql7.2.1.
> Is this bug fixed? If yes: How can I achive this fix?
> If not: How can I make postgresql work on RH7.3?
>
> Shouldn't the FAQ mention the issue?
>
> If some should be a bit confused: The error appears when operating on dates before the epoc:
>
> rhklan=> create table test(day date);
> CREATE
> rhklan=> insert into test values('1969-2-2');
> INSERT 824159 1
> rhklan=> select age(now(),day) from test;
> ERROR: Unable to convert date to tm
We discussed this major issue at first a month ago. Seems glibc now
doesn't want us to access pre-1970 dates because of a ultra-strict
reading of the standards. We haven't come up with a solution yet, but
one idea is to mask over glibc on those platforms and allow such
pre-1970 access. Right now, the only thing I can think of is to
complain to the glibc folks because most/all of our developers think
glibc is now broken in this regard. There may be a workaround in 7.3.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2002-07-05 17:38:58 | Particular query optimization question |
Previous Message | Markus Wollny | 2002-07-05 17:20:05 | Performance of ODBC-Driver /w IIS5.0/ColdFusion |