From: | Олег Самойлов <splarv(at)ya(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Mistyped message severity |
Date: | 2018-12-26 17:37:04 |
Message-ID: | 4557EA65-0144-4B51-849C-411613096B42@ya.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Very interesting. I think the same for LOG and log messages? IMHO, it’s worth to add to the documentation.
> 26 дек. 2018 г., в 20:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> написал(а):
>
> =?utf-8?q?PG_Doc_comments_form?= <noreply(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2018-12-27 10:53:18 | Re: tickling the lesser contributor's withering ego |
Previous Message | Tom Lane | 2018-12-26 17:31:29 | Re: Mistyped message severity |