Re: Interesting failure mode for initdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Interesting failure mode for initdb
Date: 2001-03-10 15:55:24
Message-ID: 16474.984239724@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-03-10 16:03:55 Re: Interesting failure mode for initdb
Previous Message Peter Eisentraut 2001-03-10 09:38:36 Re: Interesting failure mode for initdb