Horton

Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)

Dave Page <dpage@postgresql.org>

View thread View on postgr.es
From: "Dave Page" <dpage@postgresql.org>
To: "Magnus Hagander" <magnus@hagander.net>
Cc: "Bruce Momjian" <bruce@momjian.us>, "Tom Lane" <tgl@sss.pgh.pa.us>, "Peter Eisentraut" <peter_e@gmx.net>, pgsql-hackers@postgresql.org, "Alvaro Herrera" <alvherre@commandprompt.com>, "Simon Riggs" <simon@2ndquadrant.com>, "Neil Conway" <neilc@samurai.com>, "Gregory Stark" <stark@enterprisedb.com>, "Jonah H. Harris" <jonah.harris@gmail.com>
Date: 2008-02-05T16:18:29Z
Lists: pgsql-hackers 
On Feb 5, 2008 3:27 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Thu, Jan 31, 2008 at 11:02:03AM -0500, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > I would be satisfied with that if I thought people would actually read
> > > the message.  My complaint is really directed at certain admin packages
> > > (and they know who they are) that invoke pg_dump *by default*, behind
> > > the user's back, with -i.
> >
> > Oh?  That isn't good.
>
> Right. Dave - why do we do that? ;-)

I didn't realise we did until Tom mentioned it - I didn't write that code.

Please go ahead and remove the -i - it's not like users cannot cannot
specify which set of pg utilities to use if they need a specific
version.

/D