| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Kevin Field <kev(at)brantaero(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: client_min_messages not suppressing messages in psql nor pgAdminIII |
| Date: | 2014-01-21 17:04:03 |
| Message-ID: | CAMkU=1xU6mrrdLTjh5MrXxjyzJkEr5Q6sZjeSRaXpEcAQWZphw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 21, 2014 at 7:57 AM, Kevin Field <kev(at)brantaero(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-21 17:21:44 | Re: client_min_messages not suppressing messages in psql nor pgAdminIII |
| Previous Message | Stefan Warten | 2014-01-21 16:13:55 | Re: pg_upgrade fails: "Mismatch of relation OID in database" - 9.2.4 to 9.3.2 |