Re: client_min_messages not suppressing messages in psql nor pgAdminIII

Поиск
Список
Период
Сортировка
От Kevin Field
Тема Re: client_min_messages not suppressing messages in psql nor pgAdminIII
Дата
Msg-id 52DED2E5.5020107@brantaero.com
обсуждение исходный текст
Ответ на Re: client_min_messages not suppressing messages in psql nor pgAdminIII  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
>> 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.

Thank you very much Jeff and Tom for the clarification!  This was
bugging me, and I'm glad to know the right thing to do now.  :)

Kev


В списке pgsql-general по дате отправления:

Предыдущее
От: Joel Hoffman
Дата:
Сообщение: Re: Is there a way to address all elements of JSON array when creating a constraint in PosgreSQL?
Следующее
От: Ken Tanzer
Дата:
Сообщение: pg_config problems on PG9.3/Centos?