Horton

Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable

Gregory Stark <stark@enterprisedb.com>

View thread View on postgr.es
From: Gregory Stark <stark@enterprisedb.com>
To: "Bruce Momjian" <bruce@momjian.us>
Cc: "Dimitri Fontaine" <dfontaine@hi-media.com>, <pgsql-hackers@postgresql.org>, "Tom Lane" <tgl@sss.pgh.pa.us>, "Simon Riggs" <simon@2ndquadrant.com>, "Neil Conway" <neilc@samurai.com>, "Jonah H. Harris" <jonah.harris@gmail.com>
Date: 2008-01-31T16:08:38Z
Lists: pgsql-hackers 
"Bruce Momjian" <bruce@momjian.us> writes:

> Dimitri Fontaine wrote:
> -- Start of PGP signed section.
>> Hi,
>> 
>> Le jeudi 31 janvier 2008, Tom Lane a ?crit?:
>> > We have *never* promised that pg_dump version N could dump from server
>> > version N+1 .., in fact, personally I'd like to make that case be a hard
>> > error, rather than something people could override with -i.
>> 
>> Are you thinking about next major or minor version ? All the same?
>> Is there some real good reason not to dump say 8.2.6 server with the pg_dump 
>> from an 8.2.5 installation?
>
> They are talking about cross-major dumps, 8.2 pg_dump dumping an 8.3
> database.  They are saying that should be disallowed.

And just to be clearly *only* cross-major dumps with an *older* pg_dump than
the database. Dumping with a newer pg_dump than the database is the
recommended way to do cross-major dumps.

Perhaps we can have something like --force-unsupported-incompatible-connections

1/2 :)

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's PostGIS support!