From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Dwayne Bailey <dwayne(at)mika(dot)com> |
Cc: | Maarten Boekhold <maartenb(at)dutepp2(dot)et(dot)tudelft(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Timezone problems / HAVE_INT_TIMEZINE |
Date: | 1998-03-19 15:42:43 |
Message-ID: | 35113CF3.7D6CFCD8@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> It's a moot point, anyway. I put explicit calls in to the
> startup, and it made no difference in the result. It's likely to
> be a 32/64 bit issue somewhere that I haven't located yet. It
> really shouldn't be that hard to track down. Since the output is
> different from the input by a consistance amount (19 years +- a
> few days) it can only be in one of 4 places, AFAIK: parsing
> input, storing value, retrieving value, or generating output. My
> bet is on the retrieve phase, but we'll see.
Didn't this stuff work for v6.2.1, even on Alpha? afaik nothing around
this adt code changed recently...
- Tom
I moved to another job recently so left my dozen Alphas and don't have
access to man pages on them :( Have you tried compiling with
HAVE_INT_TIMEZONE disabled?
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas | 1998-03-19 15:57:19 | AW: [HACKERS] Re: PL/PgSQL discussion |
Previous Message | Zeugswetter Andreas | 1998-03-19 15:42:15 | AW: [HACKERS] Begin statement again |