Document a few more regression test hazards.

Michael Paquier, reviewed by Christian Kruse

1 files changed, 18 insertions, 2 deletions

diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml
index 2b955870b9e..edb476aa2f8 100644
--- a/doc/src/sgml/regress.sgml
+++ b/doc/src/sgml/regress.sgml
@@ -125,7 +125,9 @@ gmake installcheck-parallel
 </screen>
    The tests will expect to contact the server at the local host and the
    default port number, unless directed otherwise by <envar>PGHOST</envar> and
-   <envar>PGPORT</envar> environment variables.
+   <envar>PGPORT</envar> environment variables.  The tests will be run in a
+   database named <literal>regression</>; any existing database by this name
+   will be dropped.
   </para>
 
   <para>
@@ -147,7 +149,9 @@ gmake installcheck
 </screen>
    The <filename>contrib</> modules must have been built and installed first.
    You can also do this in a subdirectory of <filename>contrib</> to run
-   the tests for just one module.
+   the tests for just one module.  Tests of <literal>contrib</> modules will
+   be run in a database named <literal>contrib_regression</>; any existing
+   database by this name will be dropped.
   </para>
   </sect2>
 
@@ -471,6 +475,18 @@ diff results/random.out expected/random.out
      not worry unless the random test fails repeatedly.
     </para>
    </sect2>
+
+   <sect2>
+    <title>Configuration Parameters</title>
+
+    <para>
+     When running the tests against an existing installation, some non-default
+     parameter settings could cause the tests to fail.  For example, the
+     settings described in <xref linkend="runtime-config-query-enable">
+     could cause plan changes that would affect the results of tests which
+     use <command>EXPLAIN</>.
+    </para>
+   </sect2>
   </sect1>
 
 <!-- We might want to move the following section into the developer's guide. -->