Time bug fixed?

It's nice that Mr or Miss No Spam posted a message without including a usable
address for itself don't you think? If only we all were so wary of spam that we
used the nospam address and didn't sign messages I think everything would
become much clearer.

On Thu, 4 Jul 2002, Do Not Spam wrote:

[Some date related question]

--
Nigel J. Andrews

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@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026