Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id CA0459F9B90 for ; Thu, 20 Sep 2007 15:06:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 44778-06-2 for ; Thu, 20 Sep 2007 15:06:36 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by postgresql.org (Postfix) with ESMTP id 84EDD9F9BB4 for ; Thu, 20 Sep 2007 15:06:38 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so462138ugf for ; Thu, 20 Sep 2007 11:06:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=qQ8VdHg0QliAKEXQYNfcqM3aGu0fA79FgIYljam3bDs=; b=gkS3SzL5aEc4OXyta219JiT4MAYBmjI0RS04eGhKGUCEs1+Eo3ZWbWYT3b1bK0B8xYxNfuJ6xyzR8zqy8/CnCq4O3vLn/9wK0GusroZQkkrLNQkWzUw7ZtZftdlCaSb9RLF9XPiw2IaxJFlDCUJALoRgj48zwmxRcJO1/VIk8SM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pdsEqsMGNjJHmFfw7ktnnCYPscqq/vqoCCvMnFiu7wlAiLyaI0kzmDXbkdaCd9gmENzoXhyZR5uXMeA1F7S2jOdeifPwvKNnqGyyGwG2bkcQdyNvNA5yE50L/5p9i9tsoqFy3HKA/PWdVSIHu9redMguZ7ArlhrvCB4lV/YK+1A= Received: by 10.78.172.20 with SMTP id u20mr1453915hue.1190311596472; Thu, 20 Sep 2007 11:06:36 -0700 (PDT) Received: by 10.78.201.16 with HTTP; Thu, 20 Sep 2007 11:06:36 -0700 (PDT) Message-ID: <1d219a6f0709201106n24c000a7p9006f5b7257f2d69@mail.gmail.com> Date: Thu, 20 Sep 2007 14:06:36 -0400 From: "Chris Hoover" To: "Carol Walter" Subject: Re: How to update from 8.1 to 8.2 ? Cc: "Milen A. Radev" , pgsql-admin@postgresql.org In-Reply-To: <5A8931AD-0807-4641-AB12-D8565A385B58@indiana.edu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_31846_19197877.1190311596456" References: <46F294F1.50004@joops.com> <5A8931AD-0807-4641-AB12-D8565A385B58@indiana.edu> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/127 X-Sequence-Number: 26888 ------=_Part_31846_19197877.1190311596456 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 9/20/07, Carol Walter wrote: > > We just did this. I did a pg_dumpall using 8.1. Then we fired up > 8.2 while 8.1 was still running. Uploaded the data to 8.2. Then > shut 8.1 down. This allowed us to have the database unavailable for > a very short time. > > Carol Carol, If this is truely what you did, you are a very lucky person. You are always supposed to dump the old database using the new versions pg_dump/pg_dumpall. That way, pg_dump/pg_dumpall can set up the data for any changes made by the newer version. Just an fyi for those following this thread. HTH, chris ------=_Part_31846_19197877.1190311596456 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 9/20/07, Carol Walter <walterc@indiana.edu> wrote:
We just did this.  I did a pg_dumpall using 8.1.  Then we fired up
8.2 while 8.1 was still running.  Uploaded the data to 8.2.  Then
shut 8.1 down.  This allowed us to have the database unavailable for
a very short time.

Carol


Carol,

If this is truely what you did, you are a very lucky person.  You are always supposed to dump the old database using the new versions pg_dump/pg_dumpall.  That way, pg_dump/pg_dumpall can set up the data for any changes made by the newer version.

Just an fyi for those following this thread.

HTH,

chris


------=_Part_31846_19197877.1190311596456--