From: Tom Lane <tgl@sss.pgh.pa.us>
To: splarv@ya.ru
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Mistyped message severity
In-reply-to: <154584197106.6010.13448440154180762082@wrigleys.postgresql.org>
References: <154584197106.6010.13448440154180762082@wrigleys.postgresql.org>
Comments: In-reply-to =?utf-8?q?PG_Doc_comments_form?=
 <noreply@postgresql.org>
	message dated "Wed, 26 Dec 2018 16:32:51 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <31265.1545845489.1@sss.pgh.pa.us>
Date: Wed, 26 Dec 2018 12:31:29 -0500
Message-ID: <31266.1545845489@sss.pgh.pa.us>
Precedence: bulk

=?utf-8?q?PG_Doc_comments_form?= <noreply@postgresql.org> writes:
> Obviously wrongly pointed that for log messages a valid value is "INFO", but
> not "LOG" and for client messages a valid value is "LOG", but not "INFO".
> According to the description this must be quite the contrary. And, btw,
> client_min_messages accept both value.

I don't see anything particularly wrong here.  The reason INFO is not
listed for client_min_messages is that it's not a useful setting:
INFO messages will be transmitted to the client regardless of what
client_min_messages is set to.

			regards, tom lane