Re: Adding a --quiet option to initdb - Mailing list pgsql-hackers

From Devrim GUNDUZ
Subject Re: Adding a --quiet option to initdb
Date
Msg-id 1138208473.4018.32.camel@evim.gunduz.org
Whole thread Raw
In response to Re: Adding a --quiet option to initdb  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Adding a --quiet option to initdb  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Adding a --quiet option to initdb  (Thomas Hallgren <thomas@tada.se>)
Re: Adding a --quiet option to initdb  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Hi,

On Wed, 2006-01-25 at 11:28 -0500, Tom Lane wrote:
> Devrim GUNDUZ <devrim@commandprompt.com> writes:
> > Attached is a patch which adds --quiet and --q option to initdb.
>
> Why is this a good idea?

I was playing with 8.2 RPM init script and thought that instead of
directing the output to /dev/null, it would be better to use a command
line option for that. Also, we are designing a new installer project and
--quiet might help us.

I would rise this idea in -hackers before providing a patch, but since
this is my first patch, I thought it would be a good exercise for me.

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-hackers by date:

Previous
From: "Larry Rosenman"
Date:
Subject: Re: Cleaning up the INET/CIDR mess
Next
From: Robert Treat
Date:
Subject: Re: [PATCHES] postmaster/postgres merge for testing