Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id EFEE52E012F for ; Thu, 6 Mar 2008 18:56:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 21516-04 for ; Thu, 6 Mar 2008 18:56:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail.internode.com.au (mail.internode.com.au [192.83.231.27]) by postgresql.org (Postfix) with ESMTP id 8A11C2E00F9 for ; Thu, 6 Mar 2008 18:56:55 -0400 (AST) Received: from [172.16.0.221] (staffnet.internode.com.au [203.26.95.65]) by mail.internode.com.au (8.13.7/8.12.1) with ESMTP id m26MuqiI025329; Fri, 7 Mar 2008 09:26:52 +1030 (CST) Message-ID: <47D076B3.8090304@internode.com.au> Date: Fri, 07 Mar 2008 09:26:51 +1030 From: Shilpa Sudhakar User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: Tom Lane CC: pgsql-admin@postgresql.org Subject: Re: Time Zone in Postgres References: <2d6659d70803051856x652174a5ic8655d070a95db59@mail.gmail.com> <2d6659d70803052151q5861981aw3a1a2e39e3970704@mail.gmail.com> <19281.1204827832@sss.pgh.pa.us> In-Reply-To: <19281.1204827832@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on mail X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/56 X-Sequence-Number: 28539 Hi Tom, We have different databases with different versions. I checked the database with *version 8.2.4* by running the below query echo select timestamp with time zone \'epoch\' + 1206970200 \* INTERVAL \'1 second\'\; | psql template1 ?column? --------------------------- 2008-03-31 23:00:00+09:30 (1 row) This shows the wrong date. The actual result should be *2008-04-01 00:00:00+10:30 * Thanks and Regards, Tom Lane wrote: > Vishal Arora writes: > >> Hi, I've been working on a timezone issue. I am in Adelaide Australia >> and the daylight savings time this year has been changed. I am trying >> to figure out the file which is required to be changed. >> > > The easiest and best solution would be to update to a newer PG release > than 8.0.9 --- installing 8.0.15 over it would be painless and would fix > a number of problems besides this one, including some rather nasty > data-loss risks. > > If you really can't be bothered with that, you can probably use your > operating system's copy of the timezone data files (try under > /usr/share/zoneinfo for starters). > > regards, tom lane > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-admin >