Re: client_min_messages documentation typo - Mailing list pgsql-general

From Bruce Momjian
Subject Re: client_min_messages documentation typo
Date
Msg-id 20150514203158.GG23739@momjian.us
Whole thread Raw
In response to client_min_messages documentation typo  (George Woodring <george.woodring@iglass.net>)
List pgsql-general
On Fri, Dec 20, 2013 at 11:29:22AM -0500, George Woodring wrote:
>
> Currently the documentation looks like:
>
> client_min_messages (enum)
>
>     Controls which message levels are sent to the client. Valid values are
>     DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, LOG, NOTICE, WARNING, ERROR, FATAL,
>     and PANIC. Each level includes all the levels that follow it. The later the
>     level, the fewer messages are sent. The default is NOTICE. Note that LOG
>     has a different rank here than in log_min_messages.
>
> log_min_messages (enum)
>
>     Controls which message levels are written to the server log. Valid values
>     are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR,
>     LOG, FATAL, and PANIC. Each level includes all the levels that follow it.
>     The later the level, the fewer messages are sent to the log. The default is
>      WARNING. Note that LOG has a different rank here than in
>     client_min_messages. Only superusers can change this setting.
>
>
>     Shouldn't client_min_messages include INFO?

Sorry for the super-late reply, but INFO messages are always displayed
on the client so internally INFO is marked as 'hidden' so it doesn't
display as an option.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


pgsql-general by date:

Previous
From: Dennis
Date:
Subject: BDR table level replication questions
Next
From: Bruce Momjian
Date:
Subject: Re: Documentation missing bigint?