Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 4003E633D32 for ; Thu, 15 Apr 2010 10:44:53 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 57763-09 for ; Thu, 15 Apr 2010 13:44:33 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from jonah.setonhome.org (mail.setonhome.org [76.3.225.43]) by mail.postgresql.org (Postfix) with ESMTP id B3FF7634873 for ; Thu, 15 Apr 2010 10:37:05 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by jonah.setonhome.org (Postfix) with ESMTP id B9B6B6CC6E0 for ; Thu, 15 Apr 2010 09:37:11 -0400 (EDT) Received: from jonah.setonhome.org ([127.0.0.1]) by localhost (jonah.home.setonhome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xgZ8-OffiNRi; Thu, 15 Apr 2010 09:37:10 -0400 (EDT) Received: from [127.0.0.1] (unknown [76.3.225.44]) by jonah.setonhome.org (Postfix) with ESMTP id 9BC586CC6D5 for ; Thu, 15 Apr 2010 09:37:10 -0400 (EDT) Message-ID: <4BC7167E.2080504@setonhome.org> Date: Thu, 15 Apr 2010 09:37:02 -0400 From: Lewis Kapell Organization: Seton Home Study School User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Migrating from 8.3 to 8.4 on the same server References: <4e01e0bb79419eabaee763bd13ed1590@biglumber.com> In-Reply-To: <4e01e0bb79419eabaee763bd13ed1590@biglumber.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.406 tagged_above=-10 required=5 tests=AWL=-0.395, BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/188 X-Sequence-Number: 34282 On 4/14/2010 5:11 PM, Greg Sabino Mullane wrote: > If it wouldn't kill you, I'd suck up the time. All other solutions > are going to take additional expertise, prep, and testing. > > Keep in mind that if you have tables and/or databases that don't > change frequently, you can dump those beforehand to minimize > the final downtime. That's true, I had thought about that also. I guess I would save the contents of the biggest tables to flat files using the COPY command, then delete the copied rows, before doing the dump. Is what what you had in mind? Lewis