Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 608A52E0032 for ; Mon, 31 Mar 2008 09:09:27 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 53253-03 for ; Mon, 31 Mar 2008 09:09:25 -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 5482A2E002C for ; Mon, 31 Mar 2008 09:09:25 -0300 (ADT) Received: from nSoft.lt (unknown [217.117.29.29]) by vilnius.balt.net (Postfix) with ESMTP id 515D438B804 for ; Mon, 31 Mar 2008 15:09:23 +0300 (EEST) Received: from [192.168.16.191] (unknown [192.168.16.191]) by nSoft.lt (Postfix) with ESMTP id B383DBEFC1 for ; Mon, 31 Mar 2008 16:00:57 +0000 (GMT) Message-ID: <47F0D472.8070006@nsoft.lt> Date: Mon, 31 Mar 2008 15:09:22 +0300 From: Julius Tuskenis User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 CC: pgsql-admin@postgresql.org Subject: Re: what is the origin of postgreSQL time References: <47F0A958.2040608@nsoft.lt> <47F0ACCC.7070403@proventis.net> <47F0BA81.6080405@nsoft.lt> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archive-Number: 200803/274 X-Sequence-Number: 28757 Yes, it is undefined (#timezone = unknown) just like in other servers. Julius Vishal Arora rašė: > > Have you checked timezone parameter in postgresql.conf file? > > - Vishal > > > > > ------------------------------------------------------------------------ > > > Date: Mon, 31 Mar 2008 13:18:41 +0300 > > From: julius@nsoft.lt > > CC: pgsql-admin@postgresql.org > > Subject: Re: [ADMIN] what is the origin of postgreSQL time > > > > If I use select current_timestamp AT TIME ZONE 'EEST' I get good time > > (EEST - I'm in Lithuania). But how do I make postgreSQL use system time > > by default? The thing is we have 8 servers working and none of them is > > affected by this issue. Only one refuses to switch to summer time. > > > > Julius Tuskenis > > > > Thomas Markus rašė: > > > beware of timezone dst offset. try > > > select current_timestamp AT TIME ZONE 'MEST' > > > > > > thomas > > > > > > Julius Tuskenis schrieb: > > >> Hello, > > >> > > >> 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 > > >> OS: Gentoo Linux > > >> > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > > > > > > -- > > Julius Tuskenis > > Programuotojas > > UAB nSoft > > mob. +37068233050 > > > > > > -- > > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgsql-admin > > > ------------------------------------------------------------------------ > Windows Live Messenger : Get connected, share yourself, make a > difference the way you chat. Check it out! > -- Julius Tuskenis Programuotojas UAB nSoft mob. +37068233050