Re: BUG #3269: PSQL does not display error output - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #3269: PSQL does not display error output
Date
Msg-id 2829.1178915018@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #3269: PSQL does not display error output  (Bojan Jovanovic <bjovanovic@bjovanovic.com>)
Responses Re: BUG #3269: PSQL does not display error output  (Bojan Jovanovic <bjovanovic@bjovanovic.com>)
List pgsql-bugs
Bojan Jovanovic <bjovanovic@bjovanovic.com> writes:
> How would STDERR get redirected from psql?

The usual way, like "psql 2>/dev/null", but if you didn't know that then
it's unlikely you did it.

I have seen symptoms roughly like this one with really ancient SELinux
policies (the first draft of the policy tried to suppress direct writes
on /dev/tty from any Postgres executable, IIRC :-().  But I didn't think
RHEL3 had SELinux.  Do you have /usr/sbin/getenforce and if so what does
it report?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: BUG #3270: limit < 16 optimizer behaviour
Next
From: Alvaro Herrera
Date:
Subject: Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped)