detail to the logs. LOG> has a different precedence
here than in CLIENT_MIN_MESSAGES>.
+ Here is a summary of the various message types:
+
+
+ DEBUG[1-5]
+
+ This provides information for use by developers.
+
+
+
+
+ INFO
+
+ This provides information requested by the user, e.g.
+ SET>.
+
+
+
+
+ NOTICE
+
+ This provides information that may be helpful to users, e.g.
+ truncation of long identifiers, sequence creation as part of
+ SERIAL>.
+
+
+
+
+ WARNING
+
+ This provides warnings to the user, e.g. COMMIT>
+ outside a transaction.
+
+
+
+
+ ERROR
+
+ Reports the error that caused the transaction to abort.
+
+
+
+
+
+ LOG
+
+ This reports information of interest to administrators, e.g.
+ checkpoint activity.
+
+
+
+
+ FATAL
+
+ This reports why the backend session terminated.
+
+
+
+
+ PANIC
+
+ This reports why all backends restarted.
+
+
+
+
+
default is NOTICE>. Valid values are
DEBUG5>, DEBUG4>, DEBUG3>,
DEBUG2>, DEBUG1>, LOG>,
- NOTICE>, WARNING>, and ERROR>.
- Later values send less information to the user. LOG>
- has a different precedence here than in
- SERVER_MIN_MESSAGES>.
+ NOTICE>, WARNING>, and ERROR>.
+ Later values send less information to the user. LOG>
+ has a different precedence here than in
+ SERVER_MIN_MESSAGES>. Also see that section for an
+ explanation of the various values.