| Type: | enum |
| Default: | notice |
| Context: | user |
| Restart: | false |
| Values: | [debug5, debug4, debug3, debug2, debug1, log, notice, warning, error] |
Controls which message levels are sent to the client. Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, LOG, NOTICE, WARNING, and ERROR. 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.
INFO level messages are always sent to the client.
Recommendations
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.
On 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
On 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