Re: [HACKERS] [PATCHES] Adding a --quiet option to initdb

2006-01-25 Thread Devrim GUNDUZ
Hi, On Wed, 2006-01-25 at 16:32 +0100, Peter Eisentraut wrote: > > I think a command line options is better and required. > > I think we need more proof of that than a use case involving taking > screen shots. I've just explained my points as a reply to Tom's mail. Regards, -- The PostgreSQL

Re: [HACKERS] [PATCHES] Adding a --quiet option to initdb

2006-01-25 Thread Bruce Momjian
Peter Eisentraut wrote: > Devrim GUNDUZ wrote: > > We have the same options with reindexdb, for example. > > reindexdb and friends inherited that option from psql. On a green > field, they probably wouldn't have it. psql has more complex > semantics, so it's not clear whether that's the same t

Re: [HACKERS] [PATCHES] Adding a --quiet option to initdb

2006-01-25 Thread Peter Eisentraut
Devrim GUNDUZ wrote: > We have the same options with reindexdb, for example. reindexdb and friends inherited that option from psql. On a green field, they probably wouldn't have it. psql has more complex semantics, so it's not clear whether that's the same thing. > I think a command line opti

Re: [HACKERS] [PATCHES] Adding a --quiet option to initdb

2006-01-25 Thread Devrim GUNDUZ
Hi, On Wed, 2006-01-25 at 17:22 +0200, Devrim GUNDUZ wrote: > On Wed, 2006-01-25 at 09:28 -0500, Andrew Dunstan wrote: > > What's wrong with just sending stdout to /dev/null? If that eats > error > > messages too then we should probably fix initdb to send those to > > stderr. > > We have the same

Re: [HACKERS] [PATCHES] Adding a --quiet option to initdb

2006-01-25 Thread Devrim GUNDUZ
Hi Andrew, On Wed, 2006-01-25 at 09:28 -0500, Andrew Dunstan wrote: > What's wrong with just sending stdout to /dev/null? If that eats error > messages too then we should probably fix initdb to send those to > stderr. We have the same options with reindexdb, for example. I think a command line op