From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Date/time on glibc2 linux |
Date: | 1998-12-13 20:15:34 |
Message-ID: | 3469.913580134@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Thomas G. Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> ... How about if we continue to test for the other too
> and then the code can choose which one to enable. I can flip around the
> source blocks to get the right sense. I think this may help the Alpha
> port also, since I vaguely recall that Dec/Compaq (*sigh*) ran afoul of
> our tests too. And although the BSD-style TZ-in-tm seemed to be old
> fashioned, with reentrant/threaded code it is the wave of the future so
> could/should be the first choice for the code to consider.
I had some other fixes to make in configure.in today, so I went ahead
and added a call to AC_STRUCT_TIMEZONE. So the configuration symbol
HAVE_TM_ZONE is now available for use. You probably know better than
I what parts of the code have to be touched to prefer using the tm_zone
field of struct tm over the global timezone variable, so I'll leave that
part of the repair to you...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-12-13 21:04:03 | Re: [HACKERS] redolog - for discussion |
Previous Message | Bruce Momjian | 1998-12-13 19:32:30 | Re: [HACKERS] COMMIT |