Log Message:
-----------
Add a note about need to keep pg_listener vacuumed; this is true for
Slony-I 1.0.2; it should be obsolete for the next release.

Modified Files:
--------------
    slony1-engine/doc/howto:
        helpitsbroken.txt (r1.8 -> r1.9)

-------------- next part --------------
Index: helpitsbroken.txt
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/howto/helpitsbroken.txt,v
retrieving revision 1.8
retrieving revision 1.9
diff -Ldoc/howto/helpitsbroken.txt -Ldoc/howto/helpitsbroken.txt -u -w -r1.8 -r1.9
--- doc/howto/helpitsbroken.txt
+++ doc/howto/helpitsbroken.txt
@@ -243,4 +243,25 @@
 
 Those two queries could be submitted to all of the nodes via
 ddlscript() / EXECUTE SCRIPT, thus eliminating the sequence everywhere
-"at once."
+"at once."  Or they may be applied by hand to each of the nodes.
+
+13.  Performance Sucks after a while
+
+I have been running Slony-I on a node for a while, and am seeing
+system performance suffering.
+
+I'm seeing long running queries of the form:
+
+   fetch 100 from LOG;
+
+This is characteristic of pg_listener (which is the table containing
+NOTIFY data) having plenty of dead tuples in it.
+
+You need to do a VACUUM FULL on pg_listener, and need to vacuum
+pg_listener really frequently.  (Once every five minutes would likely
+be AOK.)
+
+Slon daemons vacuum a bunch of tables, and cleanup_thread.c contains a
+list of tables that are frequently vacuumed automatically.  In Slony-I
+1.0.2, pg_listener is not included.  In later versions, it will be, so
+that you probably don't need to worry about this anymore.
\ No newline at end of file