Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id B71A4B5DBDC for ; Tue, 21 Jun 2011 00:35:29 -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 34542-07 for ; Tue, 21 Jun 2011 03:35:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id 58272B5DBCB for ; Tue, 21 Jun 2011 00:35:23 -0300 (ADT) Received: from [192.168.1.7] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0LnHlS-1RGRtY2KUQ-00hbWs; Tue, 21 Jun 2011 05:35:10 +0200 Message-ID: <4E00116D.50704@2ndQuadrant.com> Date: Mon, 20 Jun 2011 23:35:09 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: How to pg_upgrade an 8.4.3 Installation References: <011001cc2f4d$4114a100$c33de300$@de> In-Reply-To: <011001cc2f4d$4114a100$c33de300$@de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:npDtY0k1U1pVg2N8xNcC4FOIQu+pm44binExJIpNOpe KVc39HGtVNo71GPa8ZrY9eY5WjBqKS9AeFhaD2Vc3Xy5oF2zih px7i7aIhqWmIT0AgLwUkPDLapY3yXLCPOOvzbtmsQGrApOol2O 8vG6SI2VJq+qif/psnMcuPYwXsDbu++Gjl4KPfPz6zUQioGrDR vgX7cCeCYhvGVPtquLhpoN4P9IVBrKRG8CNbVKBSg8= 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: 201106/128 X-Sequence-Number: 37754 On 06/20/2011 09:23 AM, Nils Gösche wrote: > Can I simply use the 9.0.4 pg_upgrade on this since the bug has been fixed > in 9.0.4, or would I first have to upgrade the 8.4 installation to 8.4.8? > Unless this 8.4 install was itself upgraded from 8.3 using pg_upgrade, you can go right from 8.4.3 to 9.0.4. The reason for the fix in 8.4.8 was to take care of people who use(d) pg_upgrade to upgrade from 8.3 to 8.4. Those people needed 8.4.8 released with the bug fix in order to correct the problem that could be in their 8.4 databases. If you did an 8.3->8.4 pg_upgrade on this system before, you might want to do the standard fix suggested using 8.4.8. But if this has always been an 8.4 system, you can just go right to 9.0.4. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books