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

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
Дата
Msg-id 937d27e10802050818n6cc3a017qec047200f3a994ed@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)  (Magnus Hagander <magnus@hagander.net>)
Список 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Problem with site doc search
Следующее
От: "Dave Page"
Дата:
Сообщение: Re: [BUGS] BUG #3909: src\tools\msvc\clean.bat clears parse.h file