From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Trond Eivind Glomsrød <teg(at)redhat(dot)com> |
Cc: | 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-06-07 05:11:22 |
Message-ID: | 200206070511.g575BMb19586@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Trond Eivind Glomsrd wrote:
> On Tue, 21 May 2002, Lamar Owen wrote:
>
> > On Tuesday 21 May 2002 11:04 am, Manuel Sugawara wrote:
> > > I see. This behavior is consistent with the fact that mktime is
> > > supposed to return -1 on error, but then is broken in every other Unix
> > > implementation that I know.
> >
> > > Any other workaround than downgrade or install FreeBSD?
> >
> > Complain to Red Hat. Loudly. However, as this is a glibc change, other
> > distributors are very likely to fold in this change sooner rather than
> > later.
>
> Relying on nonstandardized/nondocumented behaviour is a program bug, not a
> glibc bug. PostgreSQL needs fixing. Since we ship both, we're looking at
> it, but glibc is not the component with a problem.
No one has really answered the question --- if the way PostgreSQL is
using mktime() for pre-1970 dates is wrong, why do timezone databases
have pre-1970 timezone information?
I assume Linux does or the old mktime() wouldn't have worked for
pre-1970 dates.
--
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 | Joe Conway | 2002-06-07 05:18:14 | Re: revised sample SRF C function; proposed SRF API |
Previous Message | Bruce Momjian | 2002-06-07 05:04:30 | Re: Redhat 7.3 time manipulation bug |