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

From Jim C. Nasby
Subject Re: Adding a --quiet option to initdb
Date
Msg-id 20060126230008.GT3920@pervasive.com
Whole thread Raw
In response to Re: Adding a --quiet option to initdb  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Adding a --quiet option to initdb  (Andrew Dunstan <andrew@dunslane.net>)
Re: Adding a --quiet option to initdb  (Thomas Hallgren <thomas@tada.se>)
List pgsql-hackers
On Thu, Jan 26, 2006 at 11:36:15AM +0100, Peter Eisentraut wrote:
> James William Pye wrote:
> > Why should initdb give it [processing
> > information] to the user if the user didn't request it in the first
> > place?
> 
> Because it shows important information that we want the user to see.

Plus it can be a fairly long-running process on slower machines, so
providing feedback to the user is good.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Cleaning up the INET/CIDR mess
Next
From: Andrew Dunstan
Date:
Subject: Re: Adding a --quiet option to initdb