Re: AW: AW: AW: AW: AW: Re: tinterval - operator problems o n AI X

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: "'thomas(at)pgsql(dot)com'" <thomas(at)pgsql(dot)com>, <lockhart(at)fourpalms(dot)org>, Pete Forman <pete(dot)forman(at)westerngeco(dot)com>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: AW: AW: AW: AW: Re: tinterval - operator problems o n AI X
Date: 2001-01-18 23:48:06
Message-ID: Pine.LNX.4.30.0101190047180.3124-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zeugswetter Andreas SB writes:

> > You don't need to put this check into configure, you can just
> > do the check after mktime() is used.
>
> No, we need that info for the output functions that only use localtime.
> The intent is, to not use DST before 1970 on platforms that don't have
> mktime for dates before 1970.

You can't do execution time checks in configure. You're going to have to
do it at run-time.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2001-01-19 00:02:41 Re: [NOVICE] Re: Interval output format
Previous Message Peter Eisentraut 2001-01-18 23:46:53 Re: Getting configure to notice link-time vs run-time failures