Docs for standbycheck regression tests.

diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml
index c5c1e14f1e37d972d85eb6efc195dc720de22de5..6052db3e4a01377023f8407e1ad304bb732a28cb 100644 (file)
--- a/doc/src/sgml/regress.sgml
+++ b/doc/src/sgml/regress.sgml
@@ -1,4 +1,4 @@
-
+
 
  
   Regression Tests
@@ -142,6 +142,46 @@ gmake installcheck
    You can also do this in a subdirectory of contrib to run
    the tests for just one module.
   
+
+  
+   The source distribution also contains regression tests of the static
+   behaviour of Hot Standby. These tests require a running primary server
+   and a running standby server that is accepting new WAL changes from the
+   primary using either file-based log shipping or streaming replication.
+   Those servers are not automatically created for you, nor is the setup
+   documented here. Please check the various sections of the docs already
+   devoted to the required commands and related issues.
+  
+
+  
+   First create a database called "regression" on the primary.
+
+psql -h primary -c "CREATE DATABASE regression"
+
+   Next, run a preparatory script on the primary in the regression database:
+   src/test/regress/sql/hs_primary_setup.sql, and
+   allow for the changes to propagate to the standby, for example
+
+psql -h primary -f src/test/regress/sql/hs_primary_setup.sql regression
+
+   Now confirm that the default connection for the tester is the standby
+   server under test and then run standbycheck from the regression
+   directory.
+
+cd src/test/regress
+gmake standbycheck
+
+  
+
+  
+   Some extreme behaviours can also be generated on the primary using the 
+   script: src/test/regress/sql/hs_primary_extremes.sql
+   to allow the behaviour of the standby to be tested.
+  
+
+  
+   Additional automated testing may be available in later releases.
+