pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedMistyped message severity
3+ messages / 3 participants
[nested] [flat]
* Mistyped message severity
@ 2018-12-26 16:32 PG Doc comments form <noreply@postgresql.org>
2018-12-26 17:31 ` Re: Mistyped message severity Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2018-12-26 16:32 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: splarv@ya.ru
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/runtime-config-logging.html
Description:
begin cite
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.
log_min_error_statement (enum)
Controls which SQL statements that cause an error condition are recorded in
the server log. The current SQL statement is included in the log entry for
any message of the specified severity or higher. Valid values are DEBUG5,
DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR, LOG, FATAL,
and PANIC. The default is ERROR, which means statements causing errors, log
messages, fatal errors, or panics will be logged. To effectively turn off
logging of failing statements, set this parameter to PANIC. Only superusers
can change this setting.
and later
Severity Usage syslog eventlog
DEBUG1..DEBUG5 Provides successively-more-detailed information for use by
developers. DEBUG INFORMATION
INFO Provides information implicitly requested by the user, e.g., output
from VACUUM VERBOSE. INFO INFORMATION
NOTICE Provides information that might be helpful to users, e.g., notice of
truncation of long identifiers. NOTICE INFORMATION
WARNING Provides warnings of likely problems, e.g., COMMIT outside a
transaction block. NOTICE WARNING
ERROR Reports an error that caused the current command to
abort. WARNING ERROR
LOG Reports information of interest to administrators, e.g., checkpoint
activity. INFO INFORMATION
FATAL Reports an error that caused the current session to abort. ERR ERROR
PANIC Reports an error that caused all database sessions to
abort. CRIT ERROR
end cite
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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Mistyped message severity
2018-12-26 16:32 Mistyped message severity PG Doc comments form <noreply@postgresql.org>
@ 2018-12-26 17:31 ` Tom Lane <tgl@sss.pgh.pa.us>
2018-12-26 17:37 ` Re: Mistyped message severity Олег Самойлов <splarv@ya.ru>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2018-12-26 17:31 UTC (permalink / raw)
To: splarv@ya.ru; +Cc: pgsql-docs@lists.postgresql.org
=?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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Mistyped message severity
2018-12-26 16:32 Mistyped message severity PG Doc comments form <noreply@postgresql.org>
2018-12-26 17:31 ` Re: Mistyped message severity Tom Lane <tgl@sss.pgh.pa.us>
@ 2018-12-26 17:37 ` Олег Самойлов <splarv@ya.ru>
0 siblings, 0 replies; 3+ messages in thread
From: Олег Самойлов @ 2018-12-26 17:37 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-docs@lists.postgresql.org
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@sss.pgh.pa.us> написал(а):
>
> =?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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2018-12-26 17:37 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-12-26 16:32 Mistyped message severity PG Doc comments form <noreply@postgresql.org>
2018-12-26 17:31 ` Tom Lane <tgl@sss.pgh.pa.us>
2018-12-26 17:37 ` Олег Самойлов <splarv@ya.ru>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox