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

From Magnus Hagander
Subject Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
Date
Msg-id 47A8A6DD.2000208@hagander.net
Whole thread Raw
In response to Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)  ("Dave Page" <dpage@postgresql.org>)
Responses Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
List pgsql-hackers
Dave Page wrote:
> 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.

Ok, done!

//Magnus


pgsql-hackers by date:

Previous
From: Kris Jurka
Date:
Subject: Re: GSSAPI and V2 protocol
Next
From: Magnus Hagander
Date:
Subject: Re: GSSAPI and V2 protocol