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 ...

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