Message-ID: <4BE19CFC.4070101@2ndquadrant.com>
Date: Wed, 05 May 2010 12:29:48 -0400
From: Greg Smith <greg@2ndquadrant.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Jason Tan Boon Teck <tanboonteck@gmail.com>,
 pgsql-admin@postgresql.org
Subject: Re: Downgrading v8.4 database to v8.3
References: <AANLkTinx2YotvMWtFTlB4-Hq57qoxguxgavbU6rpphNX@mail.gmail.com>
	<4BE1958F.8050708@2ndquadrant.com> <3377.1273076004@sss.pgh.pa.us>
In-Reply-To: <3377.1273076004@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> That's very likely to fail, and worse to do so silently, because 8.3
> pg_dump doesn't know what's different about 8.4 system catalogs.
> I think your only real recourse in this situation is to do a plain dump
> from the 8.4 server (with 8.4 pg_dump) and then manually edit the dump
> script to remove any 8.4-only syntax.

I tried not to sound optimistic about it working.  Thought it might be 
worth a shot though, on the possibility that a simple schema might not 
trip over any of the 8.4 catalog changes.  Another idea here, along the 
path of manually editing dumps, is to dump from both 8.3 and 8.4 clients 
and look at the difference between the two, to help get an idea what 
changed syntax is responsible for the problems.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us