Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 3BF051337BFC for ; Wed, 6 Oct 2010 21:34:16 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 27992-08 for ; Thu, 7 Oct 2010 00:34:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mail.postgresql.org (Postfix) with ESMTP id 4DD4E1337BCB for ; Wed, 6 Oct 2010 21:34:08 -0300 (ADT) Received: from [192.168.1.7] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0Lio0b-1OR1IB29xl-00caMO; Thu, 07 Oct 2010 02:34:07 +0200 Message-ID: <4CAD157C.6040303@2ndquadrant.com> Date: Wed, 06 Oct 2010 20:34:04 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Marc Fromm CC: "pgsql-admin@postgresql.org" Subject: Re: newer release branch References: <8938CAF49A00EF419310D5C6F6C72E9914616B2E7D@ExchMailbox2.univ.dir.wwu.edu> In-Reply-To: <8938CAF49A00EF419310D5C6F6C72E9914616B2E7D@ExchMailbox2.univ.dir.wwu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:3lf/72q1e3anaUbp+FpmmPzyImqQQDApQ7gCKaaMGsi hiLTbnj/X8/whrUiASIL5OwoWuoPM36yYi9OCaTxI/ah0hW9XN 6makOKQEJz5DpT/CImyNiHCDgoVf3Le+j4DEtIGon9VIxeYzzS an0NNygbzoL035F+bDQryogAO0wLcBu1OEkGoZNUn/Et0t9U0G fHGkWNU+TDzqHwyfbSEiGdSnmunfi+eH4eCdC2/jm0= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/71 X-Sequence-Number: 35812 Marc Fromm wrote: > > There were no links or other helpful information provided. Has anyone > upgraded from 8.1 to the latest version 9.0.1? Can you do it in one jump? > > Can it be done using yum on a RHEL server? > As of RHEL 5.5, there is now an official postgresql84 package you can easily load. What I would do in your situation is target upgrading from 8.1 to 8.4 initially, via the dump/reload method, with the main expected problem being the type case changes already mentioned. I've saved a number of good links on this general topic onto http://wiki.postgresql.org/wiki/Version_History that should provide some additional guidance if you read through them a bit. By the time you get that done, 9.0 should be a better tested and stable release, and you can do a quick binary upgrade from 8.4 to 9.0 using the pg_upgrade utility. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us Author, "PostgreSQL 9.0 High Performance" Pre-ordering at: https://www.packtpub.com/postgresql-9-0-high-performance/book