Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 760BD2E2D82 for ; Thu, 6 Mar 2008 21:22:32 -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 64616-01-5 for ; Thu, 6 Mar 2008 21:22:11 -0400 (AST) 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 postgresql.org (Postfix) with ESMTP id 49E512E300E for ; Thu, 6 Mar 2008 21:21:14 -0400 (AST) 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 m271L3wS029380; Thu, 6 Mar 2008 20:21:04 -0500 (EST) To: Alvaro Herrera cc: Shilpa Sudhakar , pgsql-admin@postgresql.org Subject: Re: Time Zone in Postgres In-reply-to: <20080307010535.GM1751@alvh.no-ip.org> References: <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> <20080307002740.GK1751@alvh.no-ip.org> <26884.1204850383@sss.pgh.pa.us> <47D09035.4020005@internode.com.au> <20080307010535.GM1751@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Thu, 06 Mar 2008 22:05:35 -0300" Date: Thu, 06 Mar 2008 20:21:03 -0500 Message-ID: <29379.1204852863@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/67 X-Sequence-Number: 28550 Alvaro Herrera writes: > Shilpa Sudhakar wrote: >> If DST changes are done in version 8.2.5 and up, is there any way to >> recompile the timezone files in our existing versions without upgrading. > FWIW this change is also in 8.1.11. ... and 8.0.14 ... Anyway, yes, you could get the newer zoneinfo source files and run them through zic, but it's hard to see why that would be a smarter thing to do than a database update. There are known data-loss bugs in the minor version you're running, and you ought to be a lot more worried about those than about whether Postgres is a week off about the next DST transition. regards, tom lane