Log Message:
-----------
Have link to pgpool in FAQ

Add link to Freshmeat entry about Slony-I

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        faq.sgml (r1.24 -> r1.25)
        help.sgml (r1.11 -> r1.12)

-------------- next part --------------
Index: help.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/help.sgml,v
retrieving revision 1.11
retrieving revision 1.12
diff -Ldoc/adminguide/help.sgml -Ldoc/adminguide/help.sgml -u -w -r1.11 -r1.12
--- doc/adminguide/help.sgml
+++ doc/adminguide/help.sgml
@@ -49,6 +49,9 @@
 config files in an XML-based format that the tool transforms into a
 Slonik script</para></listitem>
 
+<listitem><Para><ulink url="http://freshmeat.net/projects/slonyi/">
+Freshmeat on &slony1; </ulink>
+
 </itemizedlist>
 </sect2>
 </sect1>
Index: faq.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.24
retrieving revision 1.25
diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.24 -r1.25
--- doc/adminguide/faq.sgml
+++ doc/adminguide/faq.sgml
@@ -956,19 +956,20 @@
 pg_stat_activity </envar> may show you some query that has been
 running way too long.  </para> </answer>
 
-<answer> <para> There are plans for
-<productname>PostgreSQL</productname> to have a timeout parameter,
-<envar> open_idle_transaction_timeout </envar>, which would cause old
+<answer> <para> There are plans for <productname> PostgreSQL
+</productname> to have a timeout parameter, <envar>
+open_idle_transaction_timeout </envar>, which would cause old
 transactions to time out after some period of disuse.  Buggy
 connection pool logic is a common culprit for this sort of thing.
-There are plans for <productname> pgpool </productname> to provide a
-better alternative, eventually, where connections would be shared
-inside a connection pool implemented in C.  You may have some more or
-less buggy connection pool in your Java or PHP application; if a small
-set of <emphasis> real </emphasis> connections are held in
-<productname>pgpool</productname>, that will hide from the database
-the fact that the application imagins that numerous of them are left
-idle in transaction for hours at a time.  </para> </answer>
+There are plans for <productname> <link linkend="pgpool"> pgpool
+</link> </productname> to provide a better alternative, eventually,
+where connections would be shared inside a connection pool implemented
+in C.  You may have some more or less buggy connection pool in your
+Java or PHP application; if a small set of <emphasis> real </emphasis>
+connections are held in <productname>pgpool</productname>, that will
+hide from the database the fact that the application imagines that
+numerous of them are left idle in transaction for hours at a time.
+</para> </answer>
 
 </qandaentry>