From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Kevin Field <kev(at)brantaero(dot)com>, "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:21:44 |
Message-ID: | 29980.1390324904@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> 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.
Yeah. Per elog.h:
#define INFO 17 /* Messages specifically requested by user (eg
* VACUUM VERBOSE output); always sent to
* client regardless of client_min_messages,
* but by default not sent to server log. */
You should not be using level INFO unless you are responding to an
explicit client request to get the output. If memory serves, we'd
not even have invented that level except that VACUUM VERBOSE existed
before we invented the elog levels, and we wanted to preserve its
always-print-the-results behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-01-21 18:22:34 | Re: UDP Overflow / UDP Drops on Standby Postgres Service |
Previous Message | Jeff Janes | 2014-01-21 17:04:03 | Re: client_min_messages not suppressing messages in psql nor pgAdminIII |