- 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
+ 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
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.
+ the specified
+ severity
+ or higher.
Valid values are DEBUG5,
DEBUG4, DEBUG3,
DEBUG2, DEBUG1,
- Controls which message levels are sent to the client.
- Valid values are DEBUG5>,
- DEBUG4>, DEBUG3>, DEBUG2>,
- DEBUG1>, LOG>, NOTICE>,
- WARNING>, and 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 .
+ INFO level messages are always sent to the client.
+