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.
