Re: [HACKERS] Adding a --quiet option to initdb - Mailing list pgsql-patches

From Devrim GUNDUZ
Subject Re: [HACKERS] Adding a --quiet option to initdb
Date
Msg-id 1138202813.4018.23.camel@evim.gunduz.org
Whole thread Raw
In response to Re: [HACKERS] Adding a --quiet option to initdb  (Devrim GUNDUZ <devrim@commandprompt.com>)
Responses Re: [HACKERS] Adding a --quiet option to initdb  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
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 options with reindexdb, for example. I think a
> command
> line option

(Opps...) We have the same options with reindexdb, for example. I think
a command line options is better and required.

Regards,
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/



pgsql-patches by date:

Previous
From: Devrim GUNDUZ
Date:
Subject: Re: [HACKERS] Adding a --quiet option to initdb
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Adding a --quiet option to initdb