Re: Adding a --quiet option to initdb

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, James William Pye <james(dot)pye(at)icrossing(dot)com>, Thomas Hallgren <thomas(at)tada(dot)se>, Devrim GUNDUZ <devrim(at)commandprompt(dot)com>, James William Pye <pgsql(at)jwp(dot)name>
Subject: Re: Adding a --quiet option to initdb
Date: 2006-01-26 23:00:08
Message-ID: 20060126230008.GT3920@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-01-26 23:35:33 Re: Adding a --quiet option to initdb
Previous Message Bruce Momjian 2006-01-26 22:09:34 Re: [HACKERS] [GENERAL] [PATCH] Better way to check for getaddrinfo

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2006-01-26 23:35:33 Re: Adding a --quiet option to initdb
Previous Message Bruce Momjian 2006-01-26 22:22:57 Re: pg_restore COPY error handling