#
#
# IDENTIFICATION
-# $Header: /cvsroot/pgsql/doc/src/sgml/Makefile,v 1.39 2001/09/18 12:08:26 petere Exp $
+# $Header: /cvsroot/pgsql/doc/src/sgml/Makefile,v 1.40 2001/09/21 18:37:05 petere Exp $
#
#----------------------------------------------------------------------------
JADE.text = $(JADE) $(JADEFLAGS) $(SGMLINCLUDE) -c $(CATALOG) -d stylesheet.dsl -i output-text -t sgml
-INSTALL HISTORY: % : %.html
+INSTALL HISTORY regress_README: % : %.html
@echo "|";\
- echo "| You should now take \`$<', save it as a text file in Netscape,";\
- echo "| and put it in place of the existing \`$@' file.";\
+ echo "| You should now take '$<', save it as a text file in Netscape,";\
+ echo "| and put it in place of the existing '$@' file.";\
echo "|"
INSTALL.html: standalone-install.sgml installation.sgml
$(JADE.text) -V nochunks tempfile_HISTORY.sgml >$@
rm tempfile_HISTORY.sgml
+regress_README.html: regress.sgml
+ ( echo '
+ echo ' ]>'; \
+ cat $< ) >tempfile_regress_README.sgml
+ $(JADE.text) -V nochunks tempfile_regress_README.sgml >$@
+ rm tempfile_regress_README.sgml
+
##
## Check
-
+
Documentation
The file HISTORY can be created similarly,
- using the command gmake HISTORY. The table
- of contents should be removed manually from the resulting text
- file.
-
-
- Since it does not change very often, the generation of the file
- src/test/regress/README is not fully
- automated. After building the
HTML version of
- the Administrator's Guide, convert the
- resulting files regress.html and
- regress-platform.html to text, using
-
Netscape. Then paste the text files
- together and edit them to taste (e.g., remove the navigation
- bars, remove the references to other chapters).
+ using the command gmake HISTORY. For the
+ file src/test/regress/README the command is
+ gmake regress_README.
+
-
-
-
+
+
+
-
+
-
<![%<span class="marked">flattext-install</span>-include[<productname>PostgreSQL</>]]></div>
<div class="diff add">+ <title><![%<span class="marked">standalone</span>-include[<productname>PostgreSQL</>]]></div>
<div class="diff ctx"> Installation Instructions
/usr/local/pgsql/bin/psql test
The long version is the rest of this
- flattext-install-include;[document.]]>
- flattext-install-ignore;[chapter.]]>
+ standalone-include;[document.]]>
+ standalone-ignore;[chapter.]]>
-flattext-install-ignore;[
+standalone-ignore;[
Getting The Source
foreign keys), then use the option when running
pg_dumpall. pg_dumpall does not
save large objects. Check
- flattext-install-include[the Administrator's Guide]]>
- flattext-install-ignore[]]>
+ standalone-include[the Administrator's Guide]]>
+ standalone-ignore[]]>
if you need to do this.
You can also install the new version in parallel with the old one
to decrease the downtime. These topics are discussed at length in
- flattext-install-include[the Administrator's Guide,]]>
- flattext-install-ignore[,]]>
+ standalone-include[the Administrator's Guide,]]>
+ standalone-ignore[,]]>
which you are encouraged
to read in any case.
Enables single-byte character set recode support. See
- flattext-install-include[the Administrator's Guide]]>
- flattext-install-ignore[]]> about this feature.
+ standalone-include[the Administrator's Guide]]>
+ standalone-ignore[]]> about this feature.
Allows the use of multibyte character encodings. This is
primarily for languages like Japanese, Korean, and Chinese.
Read
- flattext-install-include[the Administrator's Guide]]>
- flattext-install-ignore[]]>
+ standalone-include[the Administrator's Guide]]>
+ standalone-ignore[]]>
for details.
It is possible that some tests fail, due to differences in error
message wording or floating point results.
- flattext-install-include[The file
+ standalone-include[The file
src/test/regress/README and the
Administrator's Guide contain]]>
- flattext-install-ignore[ contains]]>
+ standalone-ignore[ contains]]>
detailed information about interpreting the test results. You can
repeat this test at any later time by issuing the same command.
-flattext-install-include;[
+standalone-include;[
Getting Started
client-side libraries (
libpq and psql) or ODBC/JDBC, no server-side;-flattext-install-include[see Administrator's Guide]]>
-flattext-install-ignore[see ]]>
+standalone-include[see Administrator's Guide]]>
+standalone-ignore[see ]]>
for instructions
-
+
Regression Tests
- Regression test instructions and analysis
-
-
+
+
Introduction
The regression tests are a comprehensive set of tests for the SQL
the regression tests are current for every official release.
+
+
+
+
Running the Tests
+
The regression test can be run against an already installed and
running server, or using a temporary installation within the build
- To run the tests after installation (see
- linkend="installation">), initialize a data area and start the
- server, as explained in , then type
+ To run the tests after installation)]]>,
+ initialize a data area and start the
+ server, , ]]> then type
default port number, unless directed otherwise by PGHOST and PGPORT
environment variables.
+
Test Evaluation
Several of the tests involve operations on geographic data about
- the Oakland/Berkeley, CA street map. The map data is expressed as
+ the Oakland/Berkeley, California street map. The map data is expressed as
polygons whose vertices are represented as pairs of double
precision numbers (decimal latitude and
longitude). Initially, some tables are created and loaded with
-
<span class="marked">Tuple</span> ordering differences
+
<span class="marked">Row</span> ordering differences
-You might see differences in which the same tuples are output in a
+You might see differences in which the same rows are output in a
different order than what appears in the expected file. In most cases
this is not, strictly speaking, a bug. Most of the regression test
scripts are not so pedantic as to use an ORDER BY for every single
-SELECT, and so their result tuple orderings are not well-defined
-according to the letter of the SQL spec. In practice, since we are
+SELECT, and so their result row orderings are not well-defined
+according to the letter of the SQL specification. In practice, since we are
looking at the same queries being executed on the same data by the same
software, we usually get the same result ordering on all platforms, and
so the lack of ORDER BY isn't a problem. Some queries do exhibit
not worry unless the random test always fails in repeated
attempts. (On the other hand, if the random test is
never reported to fail even in many trials
- of the regress tests, you probably should
+ of the regression tests, you probably should
worry.)
+
Platform-specific comparison files
+]]>
-
+
- flattext-install-ignore "IGNORE">
- flattext-install-include "INCLUDE">
+ standalone-ignore "IGNORE">
+ standalone-include "INCLUDE">
projects / postgresql.git / commitdiff