mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-15 08:20:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update README to reflect the fact that you don't have to

Browse Source 
run the regression tests with a special postmaster TZ setting anymore.
Correct a few typos too.
This commit is contained in:
Tom Lane 1998-10-24 22:21:12 +00:00
parent 82f54c9d2c
commit 29317100ae
1 changed files with 23 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
src/test/regress/README
View File

@ -26,21 +26,11 @@ Preparation
./expected/*.out files. The localization replaces macros in the source ./expected/*.out files. The localization replaces macros in the source
files with absolute pathnames and user names. files with absolute pathnames and user names.
The postmaster should be invoked with the system time zone set for It was formerly necessary to run the postmaster with system time zone
Berkeley, California. On many systems, this can be accomplished by set to PST, but this is no longer required. You can run the regression
setting the TZ environment variable before starting the postmaster tests under your normal postmaster configuration. The test script will
(for csh/bash; use set/export for some other shells): set the PGTZ environment variable to ensure that timezone-dependent tests
produce the expected results.
setenv TZ PST8PDT
date
/usr/local/pgsql/bin/postmaster -s
The "date" command above should have returned the current system time
in the PST8PDT time zone. If the PST8PDT database is not available, then
your system may have returned the time in GMT. If the PST8PDT time zone
is not available, you can set the time zone rules explicitly:
setenv TZ PST8PDT7,M04.01.0,M10.05.03
Directory Layout Directory Layout
@ -78,6 +68,9 @@ Comparing expected/actual output
The results are in files in the ./results directory. These results The results are in files in the ./results directory. These results
can be compared with results in the ./expected directory using 'diff'. can be compared with results in the ./expected directory using 'diff'.
(The test script now does this for you, and leaves the differences
in ./regression.diffs.)
The files might not compare exactly. The following paragraphs attempt The files might not compare exactly. The following paragraphs attempt
to explain the differences. to explain the differences.
@ -106,22 +99,24 @@ OID differences
DATE/TIME differences DATE/TIME differences
On many supported platforms, you can force PostgreSQL to believe that it Most of the date and time results are dependent on timezone environment.
is running in the same time zone as Berkeley, California. See details in The reference files are generated for timezone PST8PDT (Berkeley,
the section on how to run the regression tests. California) and there will be apparent failures if the tests are not
run with that timezone setting. The regression test driver sets
environment variable PGTZ to PST8PDT to ensure proper results.
If you do not explicitly set your time zone environment to PST8PDT, then There appear to be some systems which do not accept the recommended syntax
most of the date and time results will reflect your local time zone and for explicitly setting the local time zone rules; you may need to use
will fail the regression testing. a different PGTZ setting on such machines.
There appears to be some systems which do not accept the recommended syntax Some systems using older timezone libraries fail to apply daylight-savings
for explicitly setting the local time zone rules. Some systems using the corrections to pre-1970 dates, causing pre-1970 PDT times to be displayed
public domain time zone package exhibit minor problems with pre-1970 PDT in PST instead. This will result in localized differences in the test
times, representing them in PST instead. results.
FLOATING POINT differences FLOATING POINT differences
Some of the tests involve computing 64-bit (FLOAT8) number from table Some of the tests involve computing 64-bit (FLOAT8) numbers from table
columns. Differences in results involving mathematical functions of columns. Differences in results involving mathematical functions of
FLOAT8 columns have been observed. These differences occur where FLOAT8 columns have been observed. These differences occur where
different operating systems are used on the same platform ie: different operating systems are used on the same platform ie:
@ -137,7 +132,7 @@ FLOATING POINT differences
POLYGON differences POLYGON differences
Several of the tests involve operations on geographic date about the Several of the tests involve operations on geographic data about the
Oakland/Berkley CA street map. The map data is expressed as polygons Oakland/Berkley CA street map. The map data is expressed as polygons
whose vertices are represented as pairs of FLOAT8 numbers (decimal whose vertices are represented as pairs of FLOAT8 numbers (decimal
latitude and longitude). Initially, some tables are created and latitude and longitude). Initially, some tables are created and
@ -147,7 +142,7 @@ POLYGON differences
When comparing the results from different platforms, differences occur When comparing the results from different platforms, differences occur
in the 2nd or 3rd place to the right of the decimal point. The SQL in the 2nd or 3rd place to the right of the decimal point. The SQL
statements where these problems occur are the folowing: statements where these problems occur are the following:
QUERY: SELECT * from street; QUERY: SELECT * from street;
QUERY: SELECT * from iexit; QUERY: SELECT * from iexit;