Reini Urban <[EMAIL PROTECTED]> writes:
> But the time_t timezone issue is here:
>    "XSHd7 Aardvark Change Request Report"
> (ERN 20 Accept as marked, page 1177)

There is nothing whatever on that page about the datatype of the
timezone variable.

> Caldera, redhat and IRIX 6.2 at least use time_t

Red Hat certainly does not:

[EMAIL PROTECTED] include]$ grep timezone /usr/include/*h
/usr/include/time.h:   of *TIMER in the local timezone.  */
/usr/include/time.h:extern char *__tzname[2];   /* Current timezone names.  */
/usr/include/time.h:extern long int __timezone; /* Seconds west of UTC.  */
/usr/include/time.h:extern long int timezone;

But what may be more to the point is that AFAICS we make no assumption
about the exact datatype of the timezone variable.  So long as it is
some signed integer type (which surely it must be), the code will work.
I see no reason to add a configure test to test something we do not care

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to