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

Re: BUG #1672: Postgres 8.0 doesn't return errors.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory L Miller-Kramer <millerg(at)contexttech(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1672: Postgres 8.0 doesn't return errors.
Date: 2005-05-18 21:26:35
Message-ID: 25467.1116451595@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Gregory L Miller-Kramer <millerg(at)contexttech(dot)com> writes:
> I entered the statement you wanted. (show client_min_messages;) It
> returned...
>  client_min_messages
> ---------------------
>  log
> (1 row)

[ scratches head... ]  It's pretty hard to see why SHOW would display
something but error messages don't get displayed.

However, I still have a sneaking feeling that SELinux is mixed up in
this somehow.  Does "/usr/sbin/getenforce" show that enforcement is
active?  If so, does "sudo /usr/sbin/setenforce 0" change psql's
behavior?

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Mohan, RossDate: 2005-05-19 00:22:33
Subject: Re: [PORTS] Bug Report with Postgres 7.4 on AIX 5.3
Previous:From: Michael FuhrDate: 2005-05-18 14:01:06
Subject: Re: BUG #1672: Postgres 8.0 doesn't return errors.

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