Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 088239FB8B8 for ; Thu, 18 Oct 2007 16:29:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 29786-01 for ; Thu, 18 Oct 2007 16:29:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 695289FB7D9 for ; Thu, 18 Oct 2007 16:29:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9IJTinm027397; Thu, 18 Oct 2007 15:29:44 -0400 (EDT) To: Alexander Stanier cc: pgsql-admin@postgresql.org Subject: Re: Moving multiple schemas when upgrading from 8.1 to 8.2 In-reply-to: <47177426.1050801@egsgroup.com> References: <47177426.1050801@egsgroup.com> Comments: In-reply-to Alexander Stanier message dated "Thu, 18 Oct 2007 15:56:38 +0100" Date: Thu, 18 Oct 2007 15:29:44 -0400 Message-ID: <27396.1192735784@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/181 X-Sequence-Number: 27095 Alexander Stanier writes: > I also thought maybe I could run the 8.2.x pg_dump binary against the > 8.1.5 cluster? But I wasn't sure if this was 'allowed' and if it would > produce a valid data dump? Not only is that allowed, it's recommended. The case that won't work (or at least doesn't work in some combinations, I'm not sure about 8.1 vs 8.2 specifically) is trying to load the output of 8.2 pg_dump back into 8.1, since the newer pg_dump may make use of commands that didn't exist before. But for an upgrade, using the newer pg_dump is considered good practice. > Am I missing a really obvious way to accomplish this? For the record, you could also have fixed it by using pg_restore's -l and -L switches --- that is, create a table-of-contents listing, edit out the unwanted objects, and use that to select what to restore. regards, tom lane