Re: AW: AW: AW: AW: AW: AW: AW: Re: tinterval - operator proble ms o n AIX

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>
Subject: Re: AW: AW: AW: AW: AW: AW: AW: Re: tinterval - operator proble ms o n AIX
Date: 2001-01-19 19:58:42
Message-ID: 3A689C72.818F6D88@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > 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.

Nope. So far we have consensus that #ifdef <something> is the way to go
(I just made some changes to the date/time stuff to isolate the #ifdef
__CYGWIN__ garbage, and would like to avoid more cruft), but we are not
unanimous on the way to get that set.

- Thomas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ian Lance Taylor 2001-01-19 20:05:08 Re: Re: [PATCHES] s_lock.h cleanup
Previous Message Giulio Orsero 2001-01-19 19:52:16 Re: Slashdot and PostgreSQL