<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.34 2003/09/12 22:17:23 tgl Exp $ -->

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.35 2003/11/02 21:56:14 tgl Exp $ -->

<chapter id="regress">

<title id="regress-title">Regression Tests</title>

<screen>

<computeroutput>

======================

All77 tests passed.

All93 tests passed.

======================

</computeroutput>

</screen>

or otherwise a note aboutwhat tests failed. See <xref

or otherwise a note aboutwhich tests failed. See <xref

linkend="regress-evaluation"> below for more.

</para>

<note>

<para>

Because this test method runs a temporary server, it will not work

when you are the root user (the server will not start as root).

when you are the root user (sincethe server will not start as root).

If you already did the build as root, you do not have to start all

over. Instead, make the regression test directory writable by

some other user, log in as that user, and restart the tests.

<para>

The parallel regression test starts quite a few processes under your

user ID. Presently, the maximum concurrency is twenty parallel test

scripts, which means sixty processes: there's a server process, a <application>psql</>,

and usually a shell parent process for the <application>psql</> for each test script.

scripts, which means sixty processes: there's a server process, a

<application>psql</>, and usually a shell parent process for the

<application>psql</> for each test script.

So if your system enforces a per-user limit on the number of processes,

make sure this limit is at least seventy-five or so, else you may get

random-seeming failures in the parallel test. If you are not in

a position to raise the limit, you can edit the file

<filename>src/test/regress/parallel_schedule</> to split the

larger concurrent test sets into more manageable groups.

a position to raise the limit, you can cut down the degree of parallelism

by setting the <literal>MAX_CONNECTIONS</> parameter. For example,

<screen>

gmake MAX_CONNECTIONS=10 check

</screen>

runs no more than ten tests concurrently.

</para>

</tip>

<screen>

gmake SHELL=/bin/ksh check

</screen>

If no non-broken shell is available, youcan alter the parallel test

scheduleassuggested above.

If no non-broken shell is available, youmay be able to work around the

problem by limiting the number of connections,asshown above.

</para>

</tip>

<para>

If you run the tests against an already-installed server that was

initialized with a collationorder localedifferent than C then

initialized with a collation-order localeother than C, then

there may be differences due to sort order and follow-up

failures. The regression test suite is set up to handle this

problem by providing alternative result files that together are

<literal><replaceable>testname</>_<replaceable>digit</>.out</>.

The actual digit is not significant. Remember that the

regression test driver will consider all such files to be equally

valid test results. If the test results are platform-dependent,

valid test results. If the test results are platform-specific,

the technique described in <xref linkend="regress-platform">

should be used instead.

</para>

</screen>

The command above should have returned the current system time in

the <literal>PST8PDT</literal> time zone. If the <literal>PST8PDT</literal> time zone is not available,

then your system may have returned the time inGMT. If the

then your system may have returned the time inUTC. If the

<literal>PST8PDT</literal> time zone is missing, you can set the time zone

rules explicitly:

<programlisting>

which comparison file to use. So, to eliminate bogus test

<quote>failures</quote> for a particular platform, you must choose

or make a variant result file, and then add a line to the mapping

file, which is <filename>resultmap</filename>.

file, which is <filename>src/test/regress/resultmap</filename>.

</para>

<para>

MULTIBYTE = SQL_ASCII

MAXCONNOPT :=

MAXCONNOPT += --max-connections=$(MAX_CONNECTIONS)

check: all

$(SHELL) ./pg_regress --temp-install --top-builddir=$(top_builddir) --schedule=$(srcdir)/parallel_schedule --multibyte=$(MULTIBYTE)

$(SHELL) ./pg_regress --temp-install --top-builddir=$(top_builddir) --schedule=$(srcdir)/parallel_schedule --multibyte=$(MULTIBYTE)$(MAXCONNOPT)

installcheck: all

$(SHELL) ./pg_regress --schedule=$(srcdir)/serial_schedule --multibyte=$(MULTIBYTE)

$(SHELL) ./pg_regress --schedule=$(srcdir)/serial_schedule --multibyte=$(MULTIBYTE) numeric_big

bigcheck:

$(SHELL) ./pg_regress --temp-install --top-builddir=$(top_builddir) --schedule=$(srcdir)/parallel_schedule --multibyte=$(MULTIBYTE) numeric_big

$(SHELL) ./pg_regress --temp-install --top-builddir=$(top_builddir) --schedule=$(srcdir)/parallel_schedule --multibyte=$(MULTIBYTE)$(MAXCONNOPT)numeric_big

me=`basename$0`

dbname=regression

hostname=localhost

maxconnections=0

--temp-install=*)

temp_install=`expr"x$1":"x--temp-install=\(.*\)"`

shift;;

--max-connections=*)

maxconnections=`expr"x$1":"x--max-connections=\(.*\)"`

shift;;

--outputdir=*)

outputdir=`expr"x$1":"x--outputdir=\(.*\)"`

shift;;

*-*-cygwin*)

*parallel_schedule*)

if [$maxconnections-eq 0 ];then

echo Using unlimited parallel connections is likely to fail or hang on Cygwin.

echo Try\"$me --max-connections=n\" or\"gmake MAX_CONNECTIONS=n check\"

echo with n = 5 or 10if this happens.

whileread LINE

HOSTPAT=`expr"$LINE":'.*/\(.*\)='`

if [`expr"$host_platform:$compiler":"$HOSTPAT"`-ne 0 ]

TESTNAME=`expr"$LINE":'\(.*\)/'`

SUBST=`echo"$LINE"| sed's/^.*=//'`

HOSTPAT=`expr"$LINE":'.*/\(.*\)='`

if [`expr"$host_platform:$compiler":"$HOSTPAT"`-ne 0 ]

TESTNAME=`expr"$LINE":'\(.*\)/'`

SUBST=`echo"$LINE"| sed's/^.*=//'`

SUBSTLIST=`cat$TMPFILE`

case$host_platformin*-*-cygwin*)

PATH=$libdir:$PATH

export PATH

;;

*-*-cygwin*)

PATH=$libdir:$PATH

export PATH

;;

if [-d"$temp_install" ];then

if [$maxconnections-gt 0 ];then

connnum=0

test$# -gt$maxconnections&&$ECHO_N"(in groups of$maxconnections)$ECHO_C"

for namedo

(

$PSQL -d"$dbname"<"$inputdir/sql/$name.sql">"$outputdir/results/$name.out"2>&1

$PSQL -d"$dbname"<"$inputdir/sql/$name.sql">"$outputdir/results/$name.out"2>&1

)&

if [$maxconnections-gt 0 ];then

connnum=`expr\($connnum + 1\) %$maxconnections`

test$connnum -eq 0&&wait

bestfile=

bestdiff=