Re: Redhat 7.3 time manipulation bug

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Hannu Krosing <hannu(at)tm(dot)ee>, "Trond Eivind =?iso-8859-1?Q?Glomsr=F8d?=" <teg(at)redhat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Redhat 7.3 time manipulation bug
Date: 2002-05-22 13:30:05
Message-ID: 3CEB9D5D.1F8EB83A@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> IIRC the spec is not _really_ broken - it still allows the correct
> behaviour :)

Yes.

> The fact the ISO spec is broken usually means that at least one of the
> big vendors involved in ISO spec creation must have had a broken
> implementation at that time.

Right. IBM.

> Most likely they have fixed it by now ...

Nope, though I don't know for sure. Anyone here have a recent AIX
machine to test?

> Does anyone know _any_ other libc that has this behaviour ?

AIX and (I think) Irix.

Trond, do you have a suggestion on how to get this addressed at the
glibc level? Does someone within RH participate in glibc development? If
so, can we get them to champion changes which would comply with the
standard but remove this arbitrary breakage?

The changes would involve returning -1 from mktime() for dates before
1970, and using the tm_isdst flag to indicate whether a time zone
translation was not possible.

- Thomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-05-22 13:47:02 Re: Killing dead index tuples before they get vacuumed
Previous Message Hannu Krosing 2002-05-22 13:18:13 Re: Killing dead index tuples before they get vacuumed