Re: Interesting failure mode for initdb - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Interesting failure mode for initdb
Date
Msg-id 16474.984239724@sss.pgh.pa.us
Whole thread Raw
In response to Re: Interesting failure mode for initdb  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Interesting failure mode for initdb  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I've removed some of the >/dev/null's and the only undesired output I get
> is of this form:

> POSTGRES backend interactive interface
> $Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $

> backend> backend>
> POSTGRES backend interactive interface
> $Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $

That stuff comes out on stdout; all of the interesting stuff is on
stderr.  I don't have a problem with routing stdout to /dev/null.

> ISTM that the backend shouldn't print a prompt when it's non-interactive.

More trouble than it's worth, I think ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Interesting failure mode for initdb
Next
From: Tom Lane
Date:
Subject: Re: Interesting failure mode for initdb