Re: client_min_messages and INFO

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jason Dusek <jason(dot)dusek(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: client_min_messages and INFO
Date: 2016-06-23 13:49:54
Message-ID: 7630.1466689794@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jason Dusek <jason(dot)dusek(at)gmail(dot)com> writes:
> I notice that INFO is not included in the list of settable levels for
> client_min_messages:
> This seems to be true several versions back so I wonder: what is the
> rationale? Is it like the reverse of LOG?

INFO is used for cases where the user specifically requested the message
(VACUUM VERBOSE, for instance). Arguably, suppressing such a message
would break things, so you can't.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sameer Kumar 2016-06-23 15:14:18 What Causes Access Exclusive Lock?
Previous Message sudalai 2016-06-23 12:09:06 Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\