From a33fadfd6df1296fa0d3709926e2ba8c33cdeee4 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 18 Oct 2005 21:43:33 +0000
Subject: [PATCH] Add an entry to the discussion of regression test failures
 about the possibility of a failure due to stack overflow when max_stack_depth
 is not set properly for the platform.

---
 doc/src/sgml/regress.sgml | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml
index 742382af74..05749a3157 100644
--- a/doc/src/sgml/regress.sgml
+++ b/doc/src/sgml/regress.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/regress.sgml,v 1.48 2005/10/13 23:41:07 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/regress.sgml,v 1.49 2005/10/18 21:43:33 tgl Exp $ -->
 
  <chapter id="regress">
   <title id="regress-title">Regression Tests</title>
@@ -306,6 +306,21 @@ exclusion of those that don't.
     </para>
    </sect2>
 
+   <sect2>
+    <title>Insufficient stack depth</title>
+      
+    <para>
+     If the <literal>errors</literal> test results in a server crash
+     at the <literal>select infinite_recurse()</> command, it means that
+     the platform's limit on process stack size is smaller than the
+     <xref linkend="guc-max-stack-depth"> parameter indicates.  This
+     can be fixed by running the postmaster under a higher stack
+     size limit (4MB is recommended with the default value of 
+     <varname>max_stack_depth</>).  If you are unable to do that, an
+     alternative is to reduce the value of <varname>max_stack_depth</>.
+    </para>
+   </sect2>
+
    <sect2>
     <title>The <quote>random</quote> test</title>
       
-- 
2.40.0