database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-24 10:47:04 +03:00
Code

Add an entry to the discussion of regression test failures about the

Browse Source 
possibility of a failure due to stack overflow when max_stack_depth is
not set properly for the platform.
This commit is contained in:
Tom Lane 2005-10-18 21:43:33 +00:00
parent 220f2a7d15
commit a33fadfd6d
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/src/sgml/regress.sgml
View File

@ -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>