Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id C58066323FF for ; Thu, 10 Jun 2010 09:22:35 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 63290-05 for ; Thu, 10 Jun 2010 12:22:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 79C02632308 for ; Thu, 10 Jun 2010 09:22:27 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Thu, 10 Jun 2010 07:22:25 -0500 Message-Id: <4C1092AF0200002500032124@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Thu, 10 Jun 2010 07:22:23 -0500 From: "Kevin Grittner" To: , Cc: Subject: Re: Fatal Error during PITR Recovery Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201006/90 X-Sequence-Number: 34868 "Gnanakumar" wrote: > If I would like to upgrade to the latest minor version in 8.2.x > series, that is v8.2.17, how do I upgrade this [from 8.2.3 on > CentOS] without doing dump/restore? Links/documentation on this > are appreciated. From the PostgreSQL home page there is a link to: http://www.postgresql.org/docs/8.2/static/release-8-2-17.html Which contains a migration section, saying this: | A dump/restore is not required for those running 8.2.X. However, if | you are upgrading from a version earlier than 8.2.14, see the | release notes for 8.2.14. The migration section of: http://www.postgresql.org/docs/8.2/static/release-8-2-14.html says: | A dump/restore is not required for those running 8.2.X. However, if | you have any hash indexes on interval columns, you must REINDEX | them after updating to 8.2.14. Also, if you are upgrading from a | version earlier than 8.2.11, see the release notes for 8.2.11. http://www.postgresql.org/docs/8.2/static/release-8-2-11.html says: | A dump/restore is not required for those running 8.2.X. However, if | you are upgrading from a version earlier than 8.2.7, see the | release notes for 8.2.7. Also, if you were running a previous 8.2.X | release, it is recommended to REINDEX all GiST indexes after the | upgrade. http://www.postgresql.org/docs/8.2/static/release-8-2-7.html says: | A dump/restore is not required for those running 8.2.X. However, | you might need to REINDEX indexes on textual columns after | updating, if you are affected by the Windows locale issue described | below. Since you're not running Windows, that last one does not affect you; so, after stopping the server under 8.2.3 and starting it with 8.2.17, you need to rebuild any GiST indexes and rebuild any hash indexes on interval columns. -Kevin