client_min_messages
Sets the message levels that are sent to the client
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.
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.
Comments
| Type: | enum |
| Default: | notice |
| Context: | user |
| Restart: | false |
| Values: | [debug5, debug4, debug3, debug2, debug1, log, notice, warning, error] |
On StackOverflow
- INFO output despite "SET client_min_messages TO WARNING" just before
- How does 'client_min_messages' setting affect an application using libpq?
- Getting error when connecting with external redshift database in rails
- Teach Rails 3 to talk to Amazon Redshift - permission denied to set parameter "client_min_messages"
- How to suppress INFO messages when running psql scripts