Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
Date
Msg-id 20080131144726.GB8602@alvh.no-ip.org
Whole thread Raw
In response to Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Simon Riggs escribió:
> On Thu, 2008-01-31 at 11:20 -0300, Alvaro Herrera wrote:
> > > Tom Lane wrote:
> > 
> > > > in fact, personally I'd like to make that case be a hard error,
> > > > rather than something people could override with -i.
> > 
> > +1 to this idea.  TODO for 8.4?
> 
> -1 without some more planning about the effects and implications.

Effect: we would stop receiving complaints that an old pg_dump can talk
to a server that most likely is incompatible with it.  People would
learn on the spot that they must install the newer pg_dump.

Implication: you cannot dump a newer database and expect it to load on
an older server (it would work for certain versions, but not all).  So
if people have a bleeding-edge test server, they cannot migrate stuff
from it to their older production server.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Oops - BF:Mastodon just died
Next
From: Tom Lane
Date:
Subject: Re: Oops - BF:Mastodon just died