Re: client_min_messages not suppressing messages in psql nor pgAdminIII - Mailing list pgsql-general

From Jeff Janes
Subject Re: client_min_messages not suppressing messages in psql nor pgAdminIII
Date
Msg-id CAMkU=1xU6mrrdLTjh5MrXxjyzJkEr5Q6sZjeSRaXpEcAQWZphw@mail.gmail.com
Whole thread Raw
In response to client_min_messages not suppressing messages in psql nor pgAdminIII  (Kevin Field <kev@brantaero.com>)
Responses Re: client_min_messages not suppressing messages in psql nor pgAdminIII  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Jan 21, 2014 at 7:57 AM, Kevin Field <kev@brantaero.com> wrote:
This is a cross-post from http://stackoverflow.com/questions/21238209/info-output-despite-set-client-min-messages-to-warning-just-before since I'm not getting any answers there yet.

With postgresql-9.0.15 on CentOS 6.5 (accessed via pgAdminIII 1.18.1 on Win2003), I have a plperlu function that outputs an INFO message.  I want to suppress it during testing (using psql, which also behaves as below), but I can't even seem to do it from a pgAdminIII query window:

Why not use NOTICE?  INFO is supposed to be used for things the user *requested* to see (for example, by supplying the "verbose" option to one of the commands which take that option).
 
The documentation could be clearer on this, but it seems to suggest that there is no way to turn off INFO to the client.

Cheers,

Jeff

pgsql-general by date:

Previous
From: Stefan Warten
Date:
Subject: Re: pg_upgrade fails: "Mismatch of relation OID in database" - 9.2.4 to 9.3.2
Next
From: Tom Lane
Date:
Subject: Re: client_min_messages not suppressing messages in psql nor pgAdminIII