| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Date/time on glibc2 linux |
| Date: | 1998-12-13 21:06:58 |
| Message-ID: | 36742C72.F677282B@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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...
OK, I'm pretty sure it's only one or two places (yeah for modular code
:). So, should I make that change in both trees, or just in the
development tree? My recommendation is to be *really* conservative and
not change it around for v6.4.1, since there may be a supported platform
which doesn't conform to our assumptions. But I don't have a really
strong feeling about it, so if people other than Alpha and glibc2 folks
think it might be OK then...
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1998-12-13 21:45:54 | Re: [HACKERS] Date/time on glibc2 linux |
| Previous Message | The Hermit Hacker | 1998-12-13 21:04:03 | Re: [HACKERS] redolog - for discussion |