Mention Linux syslog will sync lines to disk, and describe how to

disable it.

diff --git a/doc/TODO b/doc/TODO
index 8400395ce473475cea43ec4bfc5f372457f8de8d..6da74a7748cb4e5c3a23f12883a58352a1b8358c 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,6 +1,6 @@
 TODO list for PostgreSQL
 ========================
-Last updated:      Sat Mar 13 18:17:39 EST 2004
+Last updated:      Mon Mar 15 09:06:53 EST 2004
 
 Current maintainer:    Bruce Momjian ([email protected])
 

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index f8372b4f294be7ee063a548010a97ddb734bf68a..e1af27c6ee254f827ea3422fcf23aace3a29841d 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -464,13 +464,19 @@ VACUUM
    rotation, the logrotate program can be
    configured to work with log files from
    syslog.
+  
 
+  
+   On many systems, however, syslog is not very reliable,
+   particularly with large log messages; it may truncate or drop messages
+   just when you need them the most.  Also, on linux,
+   syslog will sync each message to disk, yielding poor
+   performance.  Use a - at the start of the file name
+   in the syslog config file to disable this behavior.
   
 
   
-   On many systems, however, syslog is not very reliable, particularly
-   with large log messages; it may truncate or drop messages just when
-   you need them the most. You may find it more useful to pipe the
+   You may find it more useful to pipe the
    stderr of the postmaster to some type of
    log rotation program. If you start the server with
    pg_ctl, then the stderr of the postmaster