Adjust the default client_min_messages to WARNING.

James William Pye · James William Pye · commit 44d3b7b4ba99 · 2010-02-02T16:27:24.000-07:00
diff --git a/postgresql/documentation/changes.txt b/postgresql/documentation/changes.txt
@@ -10,6 +10,9 @@ Changes
    They are still accessible by python3 -m postgresql.bin.pg_*
  * Fix handling of unix domain sockets by pg.open and driver.connect.
    [Reported by twitter.com/rintavarustus]
+ * Set the default client_min_messages level to WARNING.
+   NOTICEs are often not desired by programmers, and py-postgresql's
+   high verbosity further irritates that case.
 
 0.9.3 released on 2010-01-01
 ----------------------------
diff --git a/postgresql/documentation/driver.txt b/postgresql/documentation/driver.txt
@@ -1565,6 +1565,7 @@ Or if use of a dictionary is desired::
 When a dictionary is given to construct the row, absent values are filled with
 `None`.
 
+.. _db_messages:
 
 Database Messages
 =================
@@ -1591,7 +1592,7 @@ propagated any further. However, if a `False` value is returned, the next
 element is checked until the list is exhausted and the message is given to
 `postgresql.sys.msghook`. The normal list of elements is as follows::
 
-	Output → Statement → Connection → Connector → Driver [→ postgresql.sys]
+	Output → Statement → Connection → Connector → Driver → postgresql.sys
 
 Where ``Output`` can be a `postgresql.api.Cursor` object produced by
 ``declare(...)`` or an implicit output management object used *internally* by
diff --git a/postgresql/documentation/gotchas.txt b/postgresql/documentation/gotchas.txt
@@ -79,21 +79,12 @@ far too verbose. However, considering that py-postgresql is a programmer's
 library, the default of high verbosity is taken with the express purpose of
 allowing the programmer to "adjust the volume" until appropriate.
 
-There are a number of ways to reduce the noise emitted by a script. In some
-cases, the alteration of the ``client_min_messages`` setting is the most
-appropriate solution::
-
-	>>> db.execute("SET client_min_messages TO WARNING;")
-
-However, py-postgresql provides some additional configuration tools and message
-hooks in order to taylor the detail into something more appropriate for a given
-application.
-
-See the PostgreSQL documentation for more information on the
-``client_min_messages`` setting, and see the Database Messages section in
-`postgresql.documentation.driver` for more information on filtering and the
-`postgresql.sys.msghook`.
+By default, py-postgresql adjusts the ``client_min_messages`` to only emit
+messages at the WARNING level or higher--ERRORs, FATALs, and PANICs.
+This reduces the number of messages generated by most connections dramatically.
 
+If further customization is needed, the :ref:`db_messages` section has
+information on overriding the default action taken with database messages.
 
 Strange TypeError using load_rows() or load_chunks()
 ----------------------------------------------------
diff --git a/postgresql/driver/pq3.py b/postgresql/driver/pq3.py
@@ -2309,7 +2309,9 @@ def __init__(self,
 			).raise_message()
 
 		# Startup message parameters.
-		tnkw = {}
+		tnkw = {
+			'client_min_messages' : 'WARNING',
+		}
 		if self.settings:
 			s = dict(self.settings)
 			if 'search_path' in self.settings:
