Thank you for your answer.
I've noticed that statement SELECT current_timestamp AT TIME ZONE
'Europe/Vilnius' returns me an error:
ERROR: time zone "Europe/Vilnius" not recognized
SQL state: 22023
Time zone Europe/Vilnius is the systems timezone. I checked in
pgsql/share/timezone the file is in there. What could be wrong?
Julius Tuskenis
Tom Lane rašė:
Julius Tuskenis <julius@xxxxxxxx> writes:
I have problem with postgreSQL current_timestramp. Where does it get its
value, because it doesnt match system time. The problem appeared after
this saturday-sunday night and is connected somehow with the daylight
saving. Now "date" on the server returns good value, but the SELECT
current_timestmap is 1 hour late.
Postgresql 8.1.4
^^^^^
I haven't checked the timezone history, but 8.1.4 was quite a few
timezone updates ago. Would a DST switch have happened this weekend
under old law where you live? If so, you need to update to a more
modern set of timezone files. Look under (probably, I don't know
gentoo) /usr/share/postgresql/timezone/
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
