From 19fd0c2e56dab228385fba427e004715ae0482c7 Mon Sep 17 00:00:00 2001
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Thu, 10 Sep 2009 15:02:46 +0000
Subject: [PATCH] Add note that the logging collector can block backends in
 high load situations.

---
 doc/src/sgml/config.sgml | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index dd37586f1c..c9603419ae 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.225 2009/09/08 17:08:36 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.226 2009/09/10 15:02:46 alvherre Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -2422,6 +2422,19 @@ local0.*    /var/log/postgresql
          is dynamic-linker failure messages).
          This parameter can only be set at server start.
        </para>
+
+       <note>
+        <para>
+          The logging collector is designed to never lose messages.  This means
+          that in case of extremely high load, server processes could be
+          blocked due to trying to send additional log messages when the
+          collector has fallen behind.  In contrast, <application>syslog</>
+          prefers to drop messages if it cannot write them, which means it's
+          less reliable in those cases but it will not block the rest of the
+          system.
+        </para>
+       </note>
+
       </listitem>
      </varlistentry>