Re: BUG #1672: Postgres 8.0 doesn't return errors. - Mailing list pgsql-bugs

From Michael Fuhr
Subject Re: BUG #1672: Postgres 8.0 doesn't return errors.
Date
Msg-id 20050517230531.GA33861@winnie.fuhr.org
Whole thread Raw
In response to BUG #1672: Postgres 8.0 doesn't return errors.  ("Gregory L Miller-Kramer" <millerg@contexttech.com>)
Responses Re: BUG #1672: Postgres 8.0 doesn't return errors.  (Gregory L Miller-Kramer <millerg@contexttech.com>)
List pgsql-bugs
On Tue, May 17, 2005 at 05:05:03PM -0400, Gregory L Miller-Kramer wrote:

> On system One I enter the database ...
> psql exdb exdb
> select misspelled_excol from extable;
>
> and an error is displayed...
> ERROR: column 'misspelled_excol' does not exist
>
> On the "Other" system (Postgres 8.0) that error is NOT displayed.
> Infact, nothing is displayed it just returns to the prompt.

As I asked in my previous message, what's the output of the following
query?

SHOW client_min_messages;

My first guess is that client_min_messages is set to "fatal" or
"panic", which, although not among the documented settings for
client_min_messages, are allowed and would have the effect you
describe:

test=> SET client_min_messages TO panic;
SET
test=> SELECT misspelled_excol FROM extable;
test=> SET client_min_messages TO notice;
SET
test=> SELECT misspelled_excol FROM extable;
ERROR:  column "misspelled_excol" does not exist

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #1672: Postgres 8.0 doesn't return errors.
Next
From: Neil Conway
Date:
Subject: Re: BUG #1671: Long interval string representation rejected