Date: Wed, 17 May 2006 15:58:45 -0500
From: "Jim C. Nasby" <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Jim C. Nasby" <decibel@decibel.org>,
	Bruce Momjian <pgman@candle.pha.pa.us>, pgsql-hackers@postgresql.org
Subject: Cross-version dumps (was: [DOCS] Mention pg_dump version portability)
Message-ID: <20060517205845.GI26212@pervasive.com>
References: <20060515202354.GM26212@pervasive.com>
	<200605152343.k4FNhK703441@candle.pha.pa.us>
	<20060517154120.GQ26212@decibel.org>
	<20775.1147882429@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20775.1147882429@sss.pgh.pa.us>
User-Agent: Mutt/1.5.11

Moving to -hackers.

On Wed, May 17, 2006 at 12:13:49PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <decibel@decibel.org> writes:
> > pg_dump -Fc | pg_restore will only match the output of pg_dump if
> > everything's the same version though, right? Or wrong? What happens if
> > pg_dump -Fc is and older version and pg_restore is the current version?
> 
> There would probably be some small differences, but 99% of pg_restore's
> output is just regurgitating SQL it finds in the dump file.

Maybe it's time to look at improving pg_restore's ability to deal with
cross-version issues, and make it the default for pg_dump. ISTM there's
been a fair amount of contortions as of late around pg_dump SQL
compatability. If the custom format at least included pg_dump version
information, and pg_restore new what version of PostgreSQL it was
restoring into, it could handle these cases more elegantly than is
possible with just dumping straight into psql. Or it might make more
sense for the custom format to be something that's less sensitive to
some of these compatability issues.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461