Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 06FAC2E006B for ; Mon, 31 Mar 2008 12:40:03 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 23669-02 for ; Mon, 31 Mar 2008 12:40:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from vilnius.balt.net (vilnius.balt.net [195.14.170.14]) by developer.postgresql.org (Postfix) with ESMTP id 46A972E0055 for ; Mon, 31 Mar 2008 12:40:01 -0300 (ADT) Received: from nSoft.lt (unknown [217.117.29.29]) by vilnius.balt.net (Postfix) with ESMTP id 9BB9C38BAB6; Mon, 31 Mar 2008 18:39:58 +0300 (EEST) Received: from [192.168.16.191] (unknown [192.168.16.191]) by nSoft.lt (Postfix) with ESMTP id 9BA19BEFC1; Mon, 31 Mar 2008 19:31:31 +0000 (GMT) Message-ID: <47F105CE.3010003@nsoft.lt> Date: Mon, 31 Mar 2008 18:39:58 +0300 From: Julius Tuskenis User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Tom Lane CC: pgsql-admin@postgresql.org Subject: Re: what is the origin of postgreSQL time References: <47F0A958.2040608@nsoft.lt> <27356.1206973434@sss.pgh.pa.us> In-Reply-To: <27356.1206973434@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archive-Number: 200803/280 X-Sequence-Number: 28763 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 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 > >