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: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "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 17:10:42
Message-ID: 1138209042.4018.34.camel@evim.gunduz.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
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 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

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-01-25 17:29:04
Subject: Re: Cleaning up the INET/CIDR mess
Previous:From: Bruce MomjianDate: 2006-01-25 17:07:18
Subject: Re: [PATCHES] Adding a --quiet option to initdb

pgsql-patches by date

Next:From: Bruce MomjianDate: 2006-01-25 17:33:51
Subject: Re: [PATCHES] Adding a --quiet option to initdb
Previous:From: Bruce MomjianDate: 2006-01-25 17:07:18
Subject: Re: [PATCHES] Adding a --quiet option to initdb

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