From: Simon Riggs Date: Sun, 2 May 2010 12:22:40 +0000 (+0000) Subject: Docs for standbycheck regression tests. X-Git-Tag: REL9_0_0~497 X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=abeb17cdaef1a6f058cd8c0ebb8e37a8a73f558f;p=pg-rex%2Fsyncrep.git Docs for standbycheck regression tests. --- diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml index c5c1e14f1e..6052db3e4a 100644 --- 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. +