database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Build src/test/regress/README during tarball making like the other

Browse Source 
generated text files.  Fix build of that file, too.

Put the text files in the right place during make dist, so there are no
extra manual steps required anymore.
This commit is contained in:
Peter Eisentraut
2006-04-06 18:54:37 +00:00
parent 9e0eff05ca
commit 0bc2a8ca65
4 changed files with 12 additions and 283 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/src/sgml/Makefile
View File

@ -2,7 +2,7 @@
#
# PostgreSQL documentation makefile
#
# $PostgreSQL: pgsql/doc/src/sgml/Makefile,v 1.75 2005/01/04 21:03:30 petere Exp $
# $PostgreSQL: pgsql/doc/src/sgml/Makefile,v 1.76 2006/04/06 18:54:36 petere Exp $
#
#----------------------------------------------------------------------------
@ -196,7 +196,8 @@ HISTORY.html: release.sgml
regress_README.html: regress.sgml
( echo '<!doctype chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" ['; \
echo '<!entity % standalone-ignore "IGNORE"> ]>'; \
echo '<!entity % standalone-ignore "IGNORE">'; \
echo '<!entity % standalone-include "INCLUDE"> ]>'; \
cat $< ) >tempfile_regress_README.sgml
$(JADE.text) -V nochunks tempfile_regress_README.sgml >$@
rm tempfile_regress_README.sgml

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

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/regress.sgml,v 1.50 2006/01/22 05:20:32 neilc Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/regress.sgml,v 1.51 2006/04/06 18:54:36 petere Exp $ -->
<chapter id="regress">
<title id="regress-title">Regression Tests</title>
@ -313,7 +313,9 @@ exclusion of those that don't.
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
<![%standalone-ignore;[<xref linkend="guc-max-stack-depth">]]>
<![%standalone-include;[<literal>max_stack_depth</literal>]]>
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