Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D86E06502A7 for ; Tue, 29 Jul 2008 18:06:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 82877-01 for ; Tue, 29 Jul 2008 18:06:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id C5B986501E9 for ; Tue, 29 Jul 2008 18:06:28 -0300 (ADT) Received: from [192.168.1.5] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m6TL8xvI023052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jul 2008 14:09:00 -0700 Subject: Re: Upgrading with WALs From: "Joshua D. Drake" To: Chris Bovitz Cc: pgsql-admin@postgresql.org In-Reply-To: <488F85BA.7030702@noaa.gov> References: <488F85BA.7030702@noaa.gov> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Tue, 29 Jul 2008 14:07:06 -0700 Message-Id: <1217365626.24458.21.camel@jd-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 29 Jul 2008 14:09:00 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/226 X-Sequence-Number: 29836 On Tue, 2008-07-29 at 16:03 -0500, Chris Bovitz wrote: > As I mentioned earlier, we are doing major upgrades to our database > servers from 8.1.3 which necessitates the use of pg_dumpall. But what > do we do with the WALs? Should we delete them? Or should we leave them > there, and the new version of PostgreSQL will pick up where they left > off? Should we turn off WAL archiving while rebuilding the database > with the pg_dumpall output? You can not use one cluster on top of the other. Once you have the new PostgreSQL installation upgraded you would remove your old one. E.g; this will be an outage, you can not do it online (without something like SlonY0. Sincerely, Joshua D. Drake > > Thanks again. > > > Chris > -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ United States PostgreSQL Association: http://www.postgresql.us/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate