AW: AW: AW: AW: AW: AW: AW: Re: tinterval - operator pr oble ms o n AIX

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Cc: "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>
Subject: AW: AW: AW: AW: AW: AW: AW: Re: tinterval - operator pr oble ms o n AIX
Date: 2001-01-19 16:38:28
Message-ID: 11C1E6749A55D411A9670001FA6879633681C8@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > We do not need any execution time checks for this at all. The objective is
> > to determine whether mktime works for any results that would be negative.
> > On AIX and IRIX all calls to mktime for dates before 1970 lead to a result of
> > -1, and the configure test is supposed to give a define for exactly that behavior.
>
> Okay, so you call mktime with a pre-1970 date once when the system starts
> up or when the particular function is first used and then save the result
> in a static variable.

Can anybody else give an OK to this approach, that affects all platforms ?
I am not convinced, that this is the way to go.

Andreas

PS: next response not before Monday, I am off now :-)

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-01-19 16:40:54 Re: Re: [PATCHES] s_lock.h cleanup
Previous Message mlw 2001-01-19 16:33:01 Re: 7.0.3 reproduceable serious select error