Index: doc/pgjdbc.xml
===================================================================
RCS file: /cvsroot/jdbc/pgjdbc/doc/pgjdbc.xml,v
retrieving revision 1.37
diff -u -r1.37 pgjdbc.xml
--- doc/pgjdbc.xml	3 Feb 2009 04:37:45 -0000	1.37
+++ doc/pgjdbc.xml	10 Mar 2009 09:27:48 -0000
@@ -2400,12 +2400,13 @@
    </note>
 
    <para>
-    There are a number of ways to enable server side prepared statements
-    depending on your application's needs.  The general method is to
-    set a threshold for a <classname>PreparedStatement</classname>.
-    An internal counter keeps track of how many times the statement has
+    By default, server side prepared statements are enabled after a
+    threshold of 5 uses of the same
+    <classname>PreparedStatement</classname> object is reached (an
+    internal counter keeps track of how many times the statement has
     been executed and when it reaches the threshold it will start to
-    use server side prepared statements.
+    use server side prepared statements). Developers are able to
+    manipulate that threshold as illustrated below.
    </para>
 
    <note>
@@ -2414,8 +2415,12 @@
      This avoids the cost of replanning the query every time, but also
      means that the planner cannot take advantage of the particular
      parameter values used in a particular execution of the query.
-     You should be cautious about enabling the use of server side prepared
-     statements globally.
+     This should be used carefully, as it may induce queries executed
+     orders of magnitude slower, for example when the planner opts for
+     a sequential scan in the prepared statement, and then the query
+     is executed with parameters which would highly benefit from an
+     index scan. You should be cautious about enabling the use of
+     server side prepared statements globally.
     </para>
    </note>