Skip to content
Snippets Groups Projects
Commit a33fadfd authored by Tom Lane's avatar Tom Lane
Browse files

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.
parent 220f2a7d
No related branches found
No related tags found
No related merge requests found
<!-- $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"> <chapter id="regress">
<title id="regress-title">Regression Tests</title> <title id="regress-title">Regression Tests</title>
...@@ -306,6 +306,21 @@ exclusion of those that don't. ...@@ -306,6 +306,21 @@ exclusion of those that don't.
</para> </para>
</sect2> </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> <sect2>
<title>The <quote>random</quote> test</title> <title>The <quote>random</quote> test</title>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment