|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/regress.sgml,v 1.48 2005/10/13 23:41:07 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/regress.sgml,v 1.49 2005/10/18 21:43:33 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="regress"> |
4 | 4 | <title id="regress-title">Regression Tests</title> |
@@ -306,6 +306,21 @@ exclusion of those that don't. |
306 | 306 | </para> |
307 | 307 | </sect2> |
308 | 308 |
|
| 309 | + <sect2> |
| 310 | + <title>Insufficient stack depth</title> |
| 311 | + |
| 312 | + <para> |
| 313 | + If the <literal>errors</literal> test results in a server crash |
| 314 | + at the <literal>select infinite_recurse()</> command, it means that |
| 315 | + the platform's limit on process stack size is smaller than the |
| 316 | + <xref linkend="guc-max-stack-depth"> parameter indicates. This |
| 317 | + can be fixed by running the postmaster under a higher stack |
| 318 | + size limit (4MB is recommended with the default value of |
| 319 | + <varname>max_stack_depth</>). If you are unable to do that, an |
| 320 | + alternative is to reduce the value of <varname>max_stack_depth</>. |
| 321 | + </para> |
| 322 | + </sect2> |
| 323 | + |
309 | 324 | <sect2> |
310 | 325 | <title>The <quote>random</quote> test</title> |
311 | 326 |
|
|