Thomas G. Lockhart wrote:
>
> Ronald Baljeu wrote:
> >
> > The time 18:41:48 has become 19:41:48. I just upgraded to v6.1 and this
> > has never happened before.
> > Platform is Linux 2.0.29. Compiler is gcc 2.7.2.1. C-library: 5.4.33
> > Any ideas?
>
> Yup. There is probably confusion in Postgres with your timezone
> character strings. I have a similar installation environment, but my
> US/Pacific timezone (PST8PDT) does not exhibit the behavior you see.
>
> Please tell me your exact timezone environment and I can run some tests:
> 1) What is your default timezone (the character strings and the long
> name)?
Err... Do you mean this?
% date '+%Z'
MET DST
The TZ environment variable is empty. I don't know how to obtain
the long name.
> 2) What does the link /etc/localtime point to?
/usr/lib/zoneinfo/Europe/Amsterdam
> 3) Is there *really* a space between "MET" and "DST"? (sheesh)
Yep.
> In looking at the Postgres code, it appears that if there is a space
> between "MET" and "DST" then that is the source of your trouble. "MET"
> is Middle Europe (Standard) Time, and "DST" is ignored as a "noop" (this
> behavior is inherited from previous versions of Postgres). If your
> timezone is set to "MEST" or to "METDST" with no space you might get the
> behavior you want.
Thanks! I'll try that. I can't test this right away, because I had
to downgrade because of this problem, in order to get our database up
again as quickly as possible.
Cheers,
Ronald
------------------------------
