Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 13D8F650344 for ; Tue, 29 Jul 2008 18:03:59 -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 78501-08 for ; Tue, 29 Jul 2008 18:03:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mmp1.nems.noaa.gov (mmp1.nems.noaa.gov [140.90.121.156]) by postgresql.org (Postfix) with ESMTP id 8EA416501E9 for ; Tue, 29 Jul 2008 18:03:56 -0300 (ADT) Received: from [10.1.10.145] ([192.46.108.142]) by mmp1.nems.noaa.gov (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTPSA id <0K4S005EWD6ILT90@mmp1.nems.noaa.gov> for pgsql-admin@postgresql.org; Tue, 29 Jul 2008 17:03:55 -0400 (EDT) Date: Tue, 29 Jul 2008 16:03:54 -0500 From: Chris Bovitz Subject: Upgrading with WALs To: pgsql-admin@postgresql.org Message-id: <488F85BA.7030702@noaa.gov> Organization: NOAA/NWS/NOHRSC MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.16 (X11/20080707) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/225 X-Sequence-Number: 29835 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? Thanks again. Chris