From c80edaaec2e0bee76b4f8f248d01f1dda8c4470c Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sat, 20 Oct 2007 04:00:38 +0000
Subject: [PATCH] Add a note pointing out that you can't log to syslog without
 tweaking the syslog configuration file (at least not on most known Unixen). I
 dunno why we hadn't had that info in the docs all along ...

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

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 563d5e131c..3d5c8cf1a8 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2299,6 +2299,25 @@ SELECT * FROM parent WHERE key = 2400;
         <varname>logging_collector</varname> must be enabled to generate 
         CSV-format log output.
        </para>
+
+       <note>
+        <para>
+         On most Unix systems, you will need to alter the configuration of
+         your system's <application>syslog</application> daemon in order
+         to make use of the <systemitem>syslog</systemitem> option for
+         <varname>log_destination</>.  <productname>PostgreSQL</productname>
+         can log to <application>syslog</application> facilities
+         <literal>LOCAL0</> through <literal>LOCAL7</> (see <xref
+         linkend="guc-syslog-facility">), but the default
+         <application>syslog</application> configuration on most platforms
+         will discard all such messages.  You will need to add something like
+<programlisting>
+local0.*    /var/log/postgresql
+</programlisting>
+         to the  <application>syslog</application> daemon's configuration file
+         to make it work.
+        </para>
+       </note>
       </listitem>
      </varlistentry>
 
-- 
2.39.5