| 类型: | enum |
| 默认: | notice |
| 上下文: | user |
| 重新开始: | false |
| 值: | [debug5, debug4, debug3, debug2, debug1, log, notice, warning, error] |
控制被发送给客户端的消息级别。有效值是DEBUG5、 DEBUG4、DEBUG3、DEBUG2、 DEBUG1、LOG、NOTICE、 WARNING、ERROR。 每个级别都包括其后的所有级别。级别越靠后，被发送的消息越少。默认值是NOTICE。 注意LOG在这里有与log_min_messages中不同的排名。
INFO 级别的消息总是被发送到客户端。
建议 [EN]
Unless doing interactive debugging, then you want it set to DEBUG1-5. If you have a client application which is confused by some of PostgreSQL's WARNINGs then you may want to set this to ERROR.
在 StackOverflow
- SET client_min_messages to specific ROLE postgres
- Changing client_min_messages and log_min_messages
- PG::InvalidParameterValue: ERROR: invalid value for parameter "client_min_messages": "panic"
- How does 'client_min_messages' setting affect an application using libpq?
- INFO output despite "SET client_min_messages TO WARNING" just before
在 pgsql-hackers
- Re: vacuum verbose detail logs are unclear; log at *start* of each stage; show allvisible/frozen/hintbits
- 回复：how to create index concurrently on partitioned table
- ALTER tbl rewrite loses CLUSTER ON index
- Re: error context for vacuum to include block number
- Re: feature idea: use index when checking for NULLs before SET NOT NULL