From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | leonbloy(at)sinectis(dot)com(dot)ar |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: nasty problem with redhat 6.2 + pg 7.02 |
Date: | 2000-09-19 20:38:02 |
Message-ID: | 12896.969395882@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
leonbloy(at)sinectis(dot)com(dot)ar writes:
> Timezone is set to America/Buenos Aires
> Changing this seems to elliminate the bug.
What did you change it *to*, exactly? And what dates did you test
after changing?
I would expect the bug to follow the DST transition date, which varies
in different timezones. Also, since it's the spring-forward transition
where you can see the problem, for zones north of the equator you'd be
needing to check the March-ish transition date not the October-ish one.
In my experience, timekeeping routines often have to distinguish between
northern and southern timezones in order to do DST properly. It could
be that you're looking at some bug in RedHat 6.2's libc that only
manifests for southern timezones. If so that might explain why the
rest of us haven't seen it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Edward Q. Bridges | 2000-09-19 20:57:11 | Re: nasty problem with redhat 6.2 + pg 7.02 |
Previous Message | Tom Lane | 2000-09-19 20:13:04 | Re: Re[4]: WTF is going on with PG_VERSION? |