Skip site navigation (1) Skip section navigation (2)

Re: BUG #3269: PSQL does not display error output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bojan Jovanovic <bjovanovic(at)bjovanovic(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>,Bojan Jovanovic <pgbojan(at)bjovanovic(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3269: PSQL does not display error output
Date: 2007-05-11 20:23:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Bojan Jovanovic <bjovanovic(at)bjovanovic(dot)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

In response to


pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2007-05-11 20:27:49
Subject: Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped)
Previous:From: Bruno Wolff IIIDate: 2007-05-11 19:10:58
Subject: Re: BUG #3270: limit < 16 optimizer behaviour

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group