Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 116D32E0035 for ; Mon, 31 Mar 2008 11:24:00 -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 00390-01 for ; Mon, 31 Mar 2008 11:23:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 41B0C2E0032 for ; Mon, 31 Mar 2008 11:23:59 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m2VENsL0027357; Mon, 31 Mar 2008 10:23:55 -0400 (EDT) To: Julius Tuskenis cc: pgsql-admin@postgresql.org Subject: Re: what is the origin of postgreSQL time In-reply-to: <47F0A958.2040608@nsoft.lt> References: <47F0A958.2040608@nsoft.lt> Comments: In-reply-to Julius Tuskenis message dated "Mon, 31 Mar 2008 12:05:28 +0300" Date: Mon, 31 Mar 2008 10:23:54 -0400 Message-ID: <27356.1206973434@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200803/279 X-Sequence-Number: 28762 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