"Bojan Jovanovic" <[EMAIL PROTECTED]> writes:
> We just upgraded to 8.2.4, and noticed that psql does not display error
> messages, e.g.:
> ...
> shp_production=# select * from asdfafsdf;
On my system I compiled 8.2.4 as well, and not only would an
interactive session like yours display no error
Bojan Jovanovic <[EMAIL PROTECTED]> writes:
> Here is the full strace of: echo "select * from sadfasdfas;" | strace psql -U
> * *
> (no sadfasfaf table..)
Well, it's sending the query as expected:
> read(0, "select * from sadfasdfas;\n", 4096) = 26
> rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG
Hi Tom,
Here is the full strace of: echo "select * from sadfasdfas;" | strace psql -U
* *
(no sadfasfaf table..)
execve("/usr/local/bin/psql", ["psql", "-U", "nutriscan_staging",
"shp_staging"], [/* 22 vars */]) = 0
uname({sys="Linux", node="new.mynutriscan.com", ...}) = 0
brk(0)
Bojan Jovanovic <[EMAIL PROTECTED]> writes:
>> RHEL3 had SELinux. Do you have /usr/sbin/getenforce and if so what does
>> it report?
> NO SElinux on this box... (don't have getenforce)
Strange. Try strace'ing the psql session to see if it's trying to write
stderr and if so what happens.
Thanks for the help Tom and others!
Nope, definitely did not intentionally redirect the STDERR..
RHEL3 had SELinux. Do you have /usr/sbin/getenforce and if so what does
it report?
NO SElinux on this box... (don't have getenforce)
On the same box I had 7.3.6 for 3 years running flawlessly..
Bojan Jovanovic <[EMAIL PROTECTED]> 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 polic
Here it is... Did not change anything from the default installation - just
compiled it,
and installed..
shp_production=# show client_min_messages
shp_production-# ;
client_min_messages
-
notice
(1 row)
shp_production=#
Is this correct?
How would STDERR get redirected fro
"Bojan Jovanovic" <[EMAIL PROTECTED]> writes:
> We just upgraded to 8.2.4, and noticed that psql does not display error
> messages, e.g.:
Works for me. Maybe you have client_min_messages set to a silly value?
Or stderr directed away from the terminal?
regards, tom lane
-
On Fri, May 11, 2007 at 01:06:02PM +, Bojan Jovanovic wrote:
> We just upgraded to 8.2.4, and noticed that psql does not display error
> messages, e.g.:
[...]
> shp_production=# select * from asdfafsdf;
> shp_production=# commit;
> ROLLBACK
What's the output of "show client_min_messages"?
--
The following bug has been logged online:
Bug reference: 3269
Logged by: Bojan Jovanovic
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: RHEL3
Description:PSQL does not display error output
Details:
Hello,
We just upgraded to 8.2.4, and
10 matches
Mail list logo
