Skip site navigation (1) Skip section navigation (2)

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

From: Devrim GUNDUZ <devrim(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Adding a --quiet option to initdb
Date: 2006-01-25 15:26:53
Message-ID: 1138202813.4018.23.camel@evim.gunduz.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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/



In response to

Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2006-01-25 15:32:34
Subject: Re: [PATCHES] Adding a --quiet option to initdb
Previous:From: Devrim GUNDUZDate: 2006-01-25 15:22:22
Subject: Re: [PATCHES] Adding a --quiet option to initdb

pgsql-patches by date

Next:From: Peter EisentrautDate: 2006-01-25 15:32:34
Subject: Re: [PATCHES] Adding a --quiet option to initdb
Previous:From: Devrim GUNDUZDate: 2006-01-25 15:22:22
Subject: Re: [PATCHES] Adding a --quiet option to initdb

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group