Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B45752E2D5F for ; Thu, 6 Mar 2008 20:28:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 33986-06 for ; Thu, 6 Mar 2008 20:27:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id C8EC12E2B73 for ; Thu, 6 Mar 2008 20:28:03 -0400 (AST) Received: from perhan.alvh.no-ip.org (190-95-27-98.bk17-dsl.surnet.cl [190.95.27.98]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m270SKSo021586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Mar 2008 16:28:24 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 80CDE47BF8; Thu, 6 Mar 2008 21:27:40 -0300 (CLST) Date: Thu, 6 Mar 2008 21:27:40 -0300 From: Alvaro Herrera To: Shilpa Sudhakar Cc: cat@zip.com.au, Tom Lane , pgsql-admin@postgresql.org Subject: Re: Time Zone in Postgres Message-ID: <20080307002740.GK1751@alvh.no-ip.org> References: <2d6659d70803051856x652174a5ic8655d070a95db59@mail.gmail.com> <2d6659d70803052151q5861981aw3a1a2e39e3970704@mail.gmail.com> <19281.1204827832@sss.pgh.pa.us> <47D076B3.8090304@internode.com.au> <20080306234653.GA20591@bunyip.billabong.weebeasite.net> <47D089CE.4040607@internode.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47D089CE.4040607@internode.com.au> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 06 Mar 2008 16:28:24 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/59 X-Sequence-Number: 28542 Shilpa Sudhakar wrote: > From 2008, the DST ends on first Sunday of April and not on the last Sun > of March. Please report this issue to the guys maintaining the TZ database upstream: http://news.gmane.org/gmane.comp.time.tz Because my country is having a TZ DST change this Saturday, a new release of tzdata is coming out tomorrow or the day after, so if this issue wasn't already reported you'll probably miss it. Still, it would be very good to be quick about it so your changes are present in the next release due shortly thereafter. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support