@@ -26,21 +26,11 @@ Preparation
2626 ./expected/*.out files. The localization replaces macros in the source
2727 files with absolute pathnames and user names.
2828
29- The postmaster should be invoked with the system time zone set for
30- Berkeley, California. On many systems, this can be accomplished by
31- setting the TZ environment variable before starting the postmaster
32- (for csh/bash; use set/export for some other shells):
33-
34- setenv TZ PST8PDT
35- date
36- /usr/local/pgsql/bin/postmaster -s
37-
38- The "date" command above should have returned the current system time
39- in the PST8PDT time zone. If the PST8PDT database is not available, then
40- your system may have returned the time in GMT. If the PST8PDT time zone
41- is not available, you can set the time zone rules explicitly:
42-
43- setenv TZ PST8PDT7,M04.01.0,M10.05.03
29+ It was formerly necessary to run the postmaster with system time zone
30+ set to PST, but this is no longer required. You can run the regression
31+ tests under your normal postmaster configuration. The test script will
32+ set the PGTZ environment variable to ensure that timezone-dependent tests
33+ produce the expected results.
4434
4535Directory Layout
4636
@@ -78,6 +68,9 @@ Comparing expected/actual output
7868
7969 The results are in files in the ./results directory. These results
8070 can be compared with results in the ./expected directory using 'diff'.
71+ (The test script now does this for you, and leaves the differences
72+ in ./regression.diffs.)
73+
8174 The files might not compare exactly. The following paragraphs attempt
8275 to explain the differences.
8376
@@ -106,22 +99,24 @@ OID differences
10699
107100DATE/TIME differences
108101
109- On many supported platforms, you can force PostgreSQL to believe that it
110- is running in the same time zone as Berkeley, California. See details in
111- the section on how to run the regression tests.
102+ Most of the date and time results are dependent on timezone environment.
103+ The reference files are generated for timezone PST8PDT (Berkeley,
104+ California) and there will be apparent failures if the tests are not
105+ run with that timezone setting. The regression test driver sets
106+ environment variable PGTZ to PST8PDT to ensure proper results.
112107
113- If you do not explicitly set your time zone environment to PST8PDT, then
114- most of thedate and timeresults will reflect your local time zone and
115- will fail the regression testing .
108+ There appear to be some systems which do not accept the recommended syntax
109+ for explicitly setting thelocal timezone rules; you may need to use
110+ a different PGTZ setting on such machines .
116111
117- There appears to be some systemswhich do not accept the recommended syntax
118- for explicitly setting the local time zone rules. Some systems using the
119- public domain time zone package exhibit minor problems with pre-1970 PDT
120- times, representing them in PST instead .
112+ Some systemsusing older timezone libraries fail to apply daylight-savings
113+ corrections to pre-1970 dates, causing pre-1970 PDT times to be displayed
114+ in PST instead. This will result in localized differences in the test
115+ results .
121116
122117FLOATING POINT differences
123118
124- Some of the tests involve computing 64-bit (FLOAT8)number from table
119+ Some of the tests involve computing 64-bit (FLOAT8)numbers from table
125120 columns. Differences in results involving mathematical functions of
126121 FLOAT8 columns have been observed. These differences occur where
127122 different operating systems are used on the same platform ie:
@@ -137,7 +132,7 @@ FLOATING POINT differences
137132
138133POLYGON differences
139134
140- Several of the tests involve operations on geographicdate about the
135+ Several of the tests involve operations on geographicdata about the
141136 Oakland/Berkley CA street map. The map data is expressed as polygons
142137 whose vertices are represented as pairs of FLOAT8 numbers (decimal
143138 latitude and longitude). Initially, some tables are created and
@@ -147,7 +142,7 @@ POLYGON differences
147142
148143 When comparing the results from different platforms, differences occur
149144 in the 2nd or 3rd place to the right of the decimal point. The SQL
150- statements where these problems occur are thefolowing :
145+ statements where these problems occur are thefollowing :
151146
152147 QUERY: SELECT * from street;
153148 QUERY: SELECT * from iexit;